New Planning Data Migration Tool !
I am glad to announce a new migration tool download here.
In his words...
PerformancePoint Server 2007 Planning Data Migration Tool
There are two primary steps to a Migration, with many tedious “sub-steps”.
The First step in the process is to Migrate the Application, this part of the process migrates:
- Security roles
- Structural metadata: all model site, model, dimension, and member set definitions
- Data Sources and Data Destinations
- Calculation rules and any associated job templates
- Form templates
- Calendar
The Second, (more tedious), step is to Migrate the Data, which accomplishes migrating the following:
- Dimension and hierarchy data
- Fact data and annotations
- Associations
The “PerformancePoint Server 2007 Planning Data Migration Tool” automates the Second set of steps, the “Data Migration” portion. The full manual process, (which requires the user to have intricate knowledge of the application), is documented in the TechNet Documentation located here:
- Preparing the Staging DB on the Source Server: http://technet.microsoft.com/en-us/library/bb838747.aspx
- Loading the Migrated Application on the Target Server: http://technet.microsoft.com/en-us/library/bb838692.aspx
There are numerous steps in each of the above two sections which need to be followed extremely carefully in order for the Data to be properly migrated into the Target Application.
The “PerformancePoint Server 2007 Planning Data Migration Tool” fully automates each of these two steps.
Note that the Application Migration, as well as the Backup \ Restore of the Staging DB from Source to Target are still manual procedures. Please refer to the above documentation to fully understand all the steps involved.
[update 6.3.08]
The following will NOT migrate in V1
- Reports
- Workflow: assignments, job, cycle definition and instances
- Users and their security role assignments
More words from the developer about the tool...
"What this all means is that if someone were to create an application, one that you know nothing about, and then they tell you to Migrate the Application along with the Data, but, they’ve provided no documentation outlining the Application, nor an SSIS packages for you to do the Prep\Load with, then YOU will then have to explore the Application and become familiar with it. You'll need to know what all the dimensions are, if any are Linked, what Hierarchies exist, etc, or, figure out how to get the information from the SQL backend. You’ll also need to find out all the Models, etc, etc. Once you have that all figured out, you then need to perform the tedious tasks outlined in the second link above, BUT… you need to make sure you do them all in the correct order for the particular application.
To give a real example. Back when I was writing this tool, a guy I worked with had to migrate a demo application that had not been created by him. The app was a relatively 'simple' app in the sense that it wasn’t overly huge or complex; it had a few Models and Dimensions; and it had a couple Model Sites and Model Sub-Sites. It also had a couple linked dimension, it had shared member data in the dimensions of the child sub-sites, etc, etc. He didn't know anything about the app since he hadn’t created it, and, he had been given the task of migrating it. The first time it took close to 3 days, because he had to learn where everything was and what to expect to see once migration was done in order to ensure it was successful. The second time he did it in a little under 2 days.
By contrast, once I finished writing the tool, it did the entire process in under 20 minutes, and I didn't know a thing about the application."
