[UPDATE – 2/23/2012]: Installing Service Pack 1 introduced the option to specify database name while creating PerformancePoint Service Application.
Creating PerfomancePoint service application in SharePoint 2010 is still a nightmare to SharePoint administrators especially when the DBAs are not big fans of GUIDs in database names. No matter we use Central Administration or PowerShell for creating PerformancePoint Service application, we don’t have any control over naming the database. It creates the PerformancePoint Service database with a name like “PPS_application_name_GUID”. But there is a workaround for changing the database name once the service application is created. Following steps describe this.
1. Stop PerformancePoint Service in Central Administration > Manage services on server
2. In the database server, using SQL Server Management Studio, back up the PerformancePoint Service database (one with the GUID in name)
3. Restore the backup into the same database server with a new name (according your naming convention). If you want to change the logical name and physical file names, you can do that as well. I have explained those steps in another post.
4. In one of the application servers, open SharePoint 2010 Management Shell (PowerShell) console and provide the following PowerShell commands.
$dbname = “name of restored database”
Set-SPPerformancePointServiceApplication -Identity “name of PerformancePoint Service application instance” -SettingsDatabase $dbname
5. Restart PerformancePoint service through Central Administration > Manage services on server.
6. Delete the old database from the server. Before deleting the database, it’s good take it offline and make sure PerformancePoint Services features are still working properly.