What would you do if you needed to change your PerformancePoint 2007 Monitoring Server Configuration database instance name? Let’s take a step back and start with some background. Microsoft BI product installations have a separate data tier option. In other words, the database is on a different machine than the actual product (like PerformancePoint). Occasionally, you may have a need to change your database server or move your data to a new database instance on the same machine. Perhaps you have a leased server and the lease expired. Maybe you have outgrown your current hardware and need a larger SQL Server machine. In all of these cases, you are going to have to backup and restore the database, ensure that you have the correct logins and permissions, and change any application configurations to use the new database instance. Let’s look into these items and see how to make the changes for PerformancePoint.
Preparing the Database Machine
I posted previously about Database Migrations – Configure Logins and Permissions. This post gives you information about:
Backup and Restoration of the SQL Database (Data contained in each database).
How to Configure logins and permissions to match the old server (data contained in the old server – like server level user accounts).
Since this post is about PerformancePoint Monitoring Server, Microsoft has posted an article specifically about how to Backup and restore Monitoring Server databases.
After you complete the work above, your new database machine is ready and the data and access to the configuration data is ready.
Configuring the PerformancePoint Server
Web Configuration File Changes
There are three web.config files on the PerformancePoint Monitoring Server that must be updated to point to the new server name. The default locations for the web.config files are listed below:
|Application / Service||Default File Location|
|Monitoring WebService:||C:\Program Files\Microsoft Office PerformancePoint Server\3.0\Monitoring\WebService|
|Preview Site:||C:\Program Files\Microsoft Office PerformancePoint Server\3.0\Monitoring\Preview|
Find each web.config file above and do a search for “PPSMonitoring”.
You should find a line that looks similar to this:
<add key=”Bpm.MonitoringConnectionString” value=”Data Source=OLD_SERVER_NAME;Initial Catalog=PPSMonitoring;Integrated Security=True” />
Replace OLD_SERVER_NAME with NEW_SERVER_NAME.
Example Configuration File Change
If your old database server name was “SQLServerOld” and your new database server name is “SQLServerNew”, you would do the following:
Current web.config file:
<add key=”Bpm.MonitoringConnectionString” value=”Data Source=SQLServerOld;Initial Catalog=PPSMonitoring;Integrated Security=True” />
Change the “Data Source” to the new database server name as shown below:
<add key=”Bpm.MonitoringConnectionString” value=”Data Source=SQLServerNew;Initial Catalog=PPSMonitoring;Integrated Security=True” />
These server name values may or may not be Fully Qualified Domain Names.
Complete the Process
After making the configuration file changes, go to the command prompt and do an “IISReset”.
You may or may not have to redeploy existing Dashboards to SharePoint. If they still work, then you won’t have to refresh them.
Some of the information on the web file configuration changes came from this Microsoft TechNet forum post.
del.icio.us Tags: Microsoft, BI, SharePoint2007, SharePoint, MOSS, SharePointServer, SQLServer, SQLServer2005, SQLServer2008, PerformancePoint, PerformancePoint2007, PerformancePointServices, MOSS2010, FUTURESULTS