Update Planning Server with Service Pack 2

Updated: 2008-12-04

Microsoft Office PerformancePoint Server 2007 with Service Pack 2 (SP2) is available as a Microsoft Installer file. This file automatically updates all installed PerformancePoint client, server, and database files and schema to the latest version. PerformancePoint client software such as the Planning Business Modeler and PerformancePoint Add-in for Excel are updated with separate .msp files. PerformancePoint Planning Server and Monitoring Server are updated by means of their own .msp files that update the configuration managers. All clients and servers must be updated with PerformancePoint Server 2007 SP2 for continued communication and operation.

Warning:
PerformancePoint Server 2007 SP2 only upgrades version 2007 PerformancePoint servers and clients. Earlier versions of PerformancePoint servers and clients need to be upgraded to version 2007 before the service pack is run. If you experience any problems with the SP2 update contact Microsoft support for further assistance.

Important:
If you are currently running PerformancePoint Server version 3.0.4102.00 or a later version, you will receive an error when you try to upgrade to Service Pack 2 (SP2). In order to successfully install SP2, you will have to run the following database update command script: AppDBpreSP2Update. This script can be found here: http://go.microsoft.com/fwlink/?LinkID=136749. After running the script, you will be able to upgrade to SP2. A future cumulative update will remove the need for this script.

Important:

If you are currently running PerformancePoint Server version 3.0.4102.00 or a later version, you will receive an error when you try to upgrade to Service Pack 2 (SP2). In order to successfully install SP2, you will have to run the following database update command script: AppDBpreSP2Update. This script can be found here: http://go.microsoft.com/fwlink/?LinkID=136749. After running the script, you will be able to upgrade to SP2. A future cumulative update will remove the need for this script.

When updating PerformancePoint Planning Server, the Staging database (StagingDB) and the Outbound database (OutboundDB) are not updated. You must create new StagingDB and OutboundDB databases as part of the update process.

This update process consists of six sequential steps. Each of these steps is discussed in detail in the articles that follow.

Note:
To upgrade from any pre-release version of the Planning server and client applications to SP2, you must first upgrade from the pre-release version to version 2007 (RTM). That upgrade must be fully completed before applying SP2. Do not use earlier versions of the Planning client applications — such as Planning Business Modeler, PerformancePoint Add-in for Excel, Planning Administration Console, or Planning Server — with the current version of Planning client applications or Planning Server, because they might cause the system to be unstable or produce unexpected results.

Note:

To upgrade from any pre-release version of the Planning server and client applications to SP2, you must first upgrade from the pre-release version to version 2007 (RTM). That upgrade must be fully completed before applying SP2.

Do not use earlier versions of the Planning client applications — such as Planning Business Modeler, PerformancePoint Add-in for Excel, Planning Administration Console, or Planning Server — with the current version of Planning client applications or Planning Server, because they might cause the system to be unstable or produce unexpected results.

Updates for client software in PerformancePoint Server 2007 SP2

Client software is updated at the binary level. Updates to Planning Business Modeler and the PerformancePoint Add-in for Excel are performance- and product-refinement–based. There are no changes to the user interface or the base behavior for either client. For a listing of current updates and performance enhancements for Planning Business Modeler and the PerformancePoint Add-in for Excel, see the PerformancePoint Server Planning SP2 Readme (http://go.microsoft.com/fwlink/?LinkID=119231).

PerformancePoint Planning Server Service Pack 2 updates

To ensure compatibility between the multiple components of the server, any update to the server requires all server binaries to be replaced with new binaries containing the new version number. Likewise all databases and applications must be updated with the new version number. Version checking is enforced so that no Web or Process service can connect to databases that have mismatched versions.

Complete prevention of mismatched service and database versions is not possible for SP2 because existing QFEs and hotfixes do not have version-checking enabled. As a result, all PerformancePoint Planning services must be shut down on all relevant computers to ensure that all services are updated to SP2. If this were not done, then any running service in the PerformancePoint system would not be updated to SP2 and would encounter errors when attempting to connect to updated SP2 databases. The entire PerformancePoint system including all services and processes should be shut down and updated with PerformancePoint Server 2007 SP2 at the same time on all computers in the PerformancePoint system. Once the SP2 binary update is complete, the PerformancePoint Planning Configuration Manager must be run on at least one computer hosting Planning Web Services to update both the system and service databases as well as all application databases. Once the Planning Configuration Manager has run successfully, the PerformancePoint system can be restarted and should function correctly.

Services should not be added or removed until after PerformancePoint Server 2007 SP2 has been successfully installed and the host computers tested.

The existing "upgrade" command in PPSCmd.exe has been deprecated.

Updates for databases

When the PerformancePoint Service and System databases are upgraded as part of SP2, the following are updated:

Database schema
A new row/field added: DBSchemaVersion

After the PerformancePoint Server SP2 upgrade, all PerformancePoint databases, including any existing or new application databases, are required to be the same version. Version-checking is based on the value in the DBSchemaVersion row/field. The databases will not be usable until they have been upgraded to SP2. The status of all SP2 application database upgrades is captured in the PPSUpgrade.log file, located in the %ProgramFiles%\Microsoft Office PerformancePoint Server\3.0 directory. This directory can be changed during configuration by the Planning Configuration Manager.

Updates for the System and Service databases

After the System and Service databases have been upgraded to SP2, all applications will be set to Offline. These applications can be brought online only after the application databases have been upgraded to SP2.

Updates for the Application database

After each application database is upgraded to SP2, all existing applications will need to be brought online manually by using Administration Console. (For more information, see Introduction to Planning Administration Console.)

Overview of the recommended SP2 update process

To avoid these version mismatch issues during the upgrade of a distributed environment, use the instructions given in the following articles.

Uninstall SP2

You can uninstall PerformancePoint Server 2007 SP2 binary files by using Features and Programs in Control Panel. However, SP2 updates to the service and system databases and all upgraded application databases cannot be removed. To remove the SP2 update from all upgraded databases, you must restore the databases from existing pre-SP2 backups using the backup and restore procedures found in the Backing up and restoring Planning Server databases section of the PerformancePoint Server 2007 Operations guide.