Data integration process

Updated: 2009-04-30

This topic provides an overview of how to create a staging database and load data from it to Planning Server clients. You can also create a script to perform Steps 2, 4, and 5 in batches by using the Planning Command Utility, as described in the Scriptable data integration topic.

Note

Synchronizing the staging database, validating data, and loading data to the application database are usually iterative processes.

Data Processes

Populating the Planning Server application database involves several processes, as shown in the following illustration:

Follow these steps to successfully load the Planning Server application database.

Step 1: Create the Staging Area Database

During application creation in Planning Administration Console or in Planning Business Modeler, a staging database is created. The staging database that is created is empty and will receive content in Step 2. For more information, see Step 1: Creating the staging database.

Step 2: Synchronize with the Application Database

You can start this step after you have an application built and models and dimensions that were created in Planning Business Modeler. When you synchronize a model or dimension, related structures and data are created from the application database into the staging area database. For more information, see Step 2: Synchronizing the staging database. To learn how to synchronize by using the Planning Command Utility, see Scriptable data integration.

Step 3: Populate the Staging Database

In Microsoft SQL Server 2005, use the existing tool set. The tool set includes SQL Server script files, SQL Server Integration Service packages, or custom code, to populate the staging area database.

Note

This is a manual process and is not supported by Planning Server.

For more information, see Step 3: Populating the staging database.

Step 4: Validate Data in the Staging Area Database

After the data is loaded into the staging area database, in SQL Server, we recommend that you run stored procedures to validate the logical business rules and foreign key relationships. For more information, see Step 4: Validating data in the staging database.

Step 5: Load Data in the Application Database

In Planning Business Modeler, load data from the staging area database into the application database. The arrow in the illustration is bidirectional because there is a partial synchronization for application changes from the application database to the staging database before data is loaded. For more information, see Step 5: Loading data from staging to application database. To learn how to load data by using the Planning Command Utility, see Scriptable data integration.

Download this book

This topic is included in the following downloadable book for easier reading and printing:

• Planning Server Planning and Architecture Guide for PerformancePoint Server 2007

See the full list of available books at Downloadable content for PerformancePoint Planning Server.