Planning Server databases
Updated: 2009-04-30
The storage tier for Planning Server includes a number of system and application databases and SQL Server 2005 Analysis Services databases. This section provides an overview of these databases. See the PerformancePoint Server 2007 Operations Guide for more information on Planning Server databases.
Planning Server includes the following relational databases and Analysis Services databases:
PPSPlanningSystem Database (system database)
PPSPlanningService Database (system database)
Application databases. There is one for each PerformancePoint Planning application, and they may be located on a different SQL Server computer from other databases.
Staging databases. There is one for each Planning application, but unlike application databases they are not required. They may also be located on different database servers from the other databases. However, staging databases must be on the same computer running SQL Server as the application database for each application.
Outbound databases. These databases are optional. They are created to extract the data from other Planning Server databases, in order to make the data available to other systems.
Analysis Services databases. There can be one for each Planning application or one for each model site within each application. They can also be located on different computers running SQL Server Analysis Services.
Planning Server System Database and Planning Service Database
For each installation of Planning Server, there is one Planning System Database (PPSPlanningSystem).
The PPSPlanningSystem Database contains the following types of data:
Planning Server security data
Planning Server type library data
Planning Server system-level configuration data
Planning Server application-level metadata
The size of the PPSPlanningSystem Database is small and remains small over time.
For each installation of Planning Server, there is one Planning Service Database (PPSPlanningService).
The PPSPlanningService database contains SQL Server Service Broker objects for various Planning Server queues. This database is also small in size and remains small, provided that the database is operating in a normal state.
The PPSPlanningSystem Database and PPSPlanningService Database can be created manually or while running Planning Server Configuration Manager.
Application databases
A full Planning Server deployment can consist of multiple Planning applications. Each Planning application has its own application database, which contains all application data, including application metadata, reference data, fact data, workflow-related data, and service broker data. This application database can grow to be large, depending on the data retention policies of your organization, the number of model sites within the application, and the construction of the models within the model sites.
The application database is created during the application creation process by using Planning Administration Console. You can select either manual or automatic creation.
Staging databases
As with application databases, there is one Planning Staging Database for each Planning application. The staging database is not required.
The staging database can be created during application creation, or it can be manually created at a later time. The Planning Staging Database must be on the same computer running SQL Server as its counterpart application database.
Outbound databases
Planning Server outbound databases contain Planning Server data that is available for other purposes, such as for use with another system. You can use Planning Administration Console to create or register databases as a data destination.
Analysis Services databases in Planning Server
Planning Server applications contain model sites, and each model site corresponds to an individual Analysis Services database. Each Analysis Services database contains one cube per model.
Download this book
This topic is included in the following downloadable book for easier reading and printing:
See the full list of available books at Downloadable content for PerformancePoint Planning Server.