KB30304: How to upgrade the MicroStrategy Enterprise Manager project from earlier pre-9.4.1 versions to the latest 9.x version

Upgrading the Strategy Enterprise Manager 9.x metadata from pre-9.4.1 versions to the 9.4.1+ version involves three possible scenarios:

1. Scenario 1: Users are satisfied with their current Enterprise Manager pre-9.4.1 project.
2. Scenario 2: Users wish to take advantage of new objects in the latest Enterprise Manager project but do not want customized objects from the earlier Enterprise Manager pre-9.4.1 project.
3. Scenario 3: Users wish to take advantage of the new objects in the latest Enterprise Manager project and they want to keep the customized objects from the earlier Enterprise Manager pre-9.4.1 project.  

Scenario 1:
If users want to use their current Enterprise Manager pre-9.4.1 project, then it is NOT necessary to re-transfer the Enterprise Manager Metadata from the Enterprise Manager Metadata in Access that is shipped with the latest version of Strategy Enterprise Manager.
 
Users can go ahead and continue to use the current Enterprise Manager pre-9.4.1 project and just need to upgrade their metadata version from that pre-9.4.1 version to the current version of Strategy. Both metadata upgrade and project upgrade are required if the Enterprise Manager project is in a separate metadata by itself. If the Enterprise Manager Project is part of a metadata that contains several other projects and that metadata was already upgraded to the latest version of Strategy, then it is sufficient for the users to just upgrade the project to the latest 9.x version.
 
 
 
Scenario 2:
Users wish to take advantage of the new objects (such as attributes, reports, metrics, etc.) in the latest Enterprise Manager project but do not want customized objects from the earlier Enterprise Manager pre-9.4.1 project.
 
Users can transfer the Enterprise Manager metadata in Access, that is shipped with the latest version of Strategy Enterprise Manager into the required database, as though installing Enterprise Manager for the first time and thus start with a new Strategy Enterprise Manager metadata. This transfer is done from Strategy Enterprise Manager Console 9.x. They should, however, NOT transfer the Enterprise Manager Warehouse. For further details on transferring the Enterprise Manager Metadata, refer to the System Administration Guide > Monitoring the System > Using Enterprise Manager and Statistics > Initialize your Enterprise Manager Production environment. The System Administration Guide is located at (by default) Start > Programs > Strategy > Product Manuals. It may also be accessed from the Documentation folder of the product install CD or download and is named Admin.pdf.
 
 
  
Scenario 3:
Users wish to take advantage of the new objects in the latest Enterprise Manager 9.4.1+ project as well as retain the customized objects from the earlier pre-9.4.1 Enterprise Manager project.
 
IMPORTANT: The instructions below assume that NO schema objects in the Enterprise Manager project were modified. Also, existing application objects were not modified. Modifications were made to copies of existing application objects or new application objects were created.
 
In this scenario, users can upgrade their existing metadata version to the latest 9.x. metadata version and also upgrade the project to the latest 9.x. version. Also, users should follow scenario 2 and create the latest 9.x Enterprise Manager project in the required metadata. After this, a project merge should be performed between both the projects. Detailed instructions are provided below.
 
Follow the steps below to accomplish Scenario 3:

• Launch Strategy Developer 9.x and connect to the old Enterprise Manager pre-9.4.1 project (metadata for this project is already upgraded to the latest 9.x metadata version).
• Duplicate this project so as to have a pre-merge copy of it as a back-up.
• Follow scenario 2 and create the latest Enterprise Manager 9.x project in the required metadata.
• Open Strategy Object Manager from All Programs > Strategy > Object Manager and then launch the project merge wizard from the Tools menu.
• The source datasource will point to the latest Enterprise Manager 9.x project. .
• The destination data source will point to the existing (old) Strategy Enterprise Manager pre-9.4.1 project whose metadata version was upgraded to the latest version of 9.x in Step #1.
  
• The conflict resolution rules should be specified as shown below. Since no out-of-the-box application and schema objects in the destination project were customized by the user, the conflict resolution for these should be set to: Replace (this will ensure that all out-of-the-box application and schema objects will have the latest definitions from the newly created Enterprise Manager 9.x project). For Configuration objects, the 'Use Existing' option should be chosen. This is because the configuration object definitions will be specific to user's environment (for example, database instance definition).
   
  

• Chose the required options to finish answering all the options on the project merge wizard and initialize the project merge process and wait for the process to complete without any errors. If any errors are received, contact Strategy Technical Support with a copy of the project merge logs.
  

 
Refer to the following Strategy Knowledge Base document for information on a warning message related to Strategy Enterprise Manager project upgrade:
 
KB38292: On Strategy Enterprise Manager console 9.x, users get a warning about upgrading the Enterprise Manager environment, even after upgrading the Enterprise Manager warehouse and statistics to the latest version.