MicroStrategy - Enterprise Manager - Upgrade

mstr-em

What are the steps to do the upgrade?

Review this page and use the instruction for "What are the steps to setup Enterprise Manager for the very first time" from the main Enterprise Manager page.

What do we have to consider when upgrading the Enterprise Manager?

If you are planning to upgrade Enterprise Manager, run a data load before you upgrade Intelligence Server. If you do not run a data load before upgrading Enterprise Manager and the projects on the Intelligence Servers, you may lose access to some statistics data.

What are the two modes that MicroStrategy offer for upgrading the Enterprise Manager?

A MicroStrategy Enterprise Manager environment includes the statistics tables, the Enterprise Manager warehouse, the Enterprise Manager console, and the Enterprise Manager project metadata. Each part of this environment needs to be upgraded. The statistics tables, warehouse, and console can be upgraded at the same time, using one of the approaches below:

  1. Complete Upgrade: All of the Intelligence Servers that are monitored by Enterprise Manager, as well as the Enterprise Manager statistics tables, warehouse, and console, are upgraded at the same time.
  2. Phased Upgrade: The Intelligence Servers are upgraded in phases, and both 8.x and 9.x Intelligence Servers must be maintained. MicroStrategy Intelligence Server 9.x can log statistics in 8.x and 9.x formats. Intelligence Server 8.x can only log statistics in 8.x formats. Use this mode if you have one Enterprise Manager instance that is used to monitor multiple Intelligence Servers, and for business reason, only some of the Intelligence Servers can be upgraded at this time. In this situation, the statistics tables, Enterprise Manager warehouse, and Enterprise Manager console should only be upgraded after all of the Intelligence Servers are upgraded. In other words, you must configure your new Intelligence Servers to log statistics in 8.x formats.

What is the correct sequence for upgrading the Enterprise Manager project metadata, the statistics tables, data warehouse, and console?

Updating the Enterprise Manager project metadata must be done separately from upgrading the statistics tables, data warehouse, and console. The Enterprise Manager project should be updated after you have upgraded the statistics and the data warehouse.

How can we upgrade the statistics tables and the data warehouse?

Upgrading the statistics tables and the data warehouse is a two-step process for each database:

  1. DDL upgrade: This step involves adding the new statistics and data warehouse tables and new columns, so that the warehouse can load data from the upgraded statistics tables.
    • The Intelligence Server statistics tables are upgraded through Configuration Wizard, or when you first open the Enterprise Manager console after upgrading it. MicroStrategy recommends upgrading the statistics tables through Configuration Wizard.
    • The Enterprise Manager data warehouse is upgraded using the Enterprise Manager console when you first open the console after upgrading it.
  2. DML upgrade: This step is optional, but recommended. It enables reporting against statistics data that was collected before the upgrade. It involves running data manipulation scripts against the statistics database to populate the new columns with data that was collected in the previous format. If the DML upgrade is not performed, Enterprise Manager may not be able to report on statistics collected under a previous version of Enterprise Manager.
    • For detailed information about the Intelligence Server statistics DML upgrade, including the scripts to run against your database, see MicroStrategy Tech Note TN39948.
    • For detailed information about the Enterprise Manager data warehouse DML upgrade, including the scripts to run against your database, see MicroStrategy Tech Note TN40014.
    • If you do not need to keep historical Enterprise Manager warehouse data available, then rather than upgrading the data warehouse you can simply create a new Enterprise Manager data warehouse, following the instructions in the Enterprise Manager chapter of the Supplemental Reference for System Administration. You must still upgrade the statistics tables.

How can we upgrade the Enterprise Manager using the Complete Upgrade approach?

Refer to What are the steps to setup Enterprise Manager for the very first time on the main Enterprise Manager page.

How can we upgrade the Enterprise Manager using the Phased approach?

See the Upgrade guide.

How can we upgrade the Enterprise Manager project and keep all of our previous customization?

After you have upgraded your statistics database and Enterprise Manager data warehouse, and performed a data load, you must update the Enterprise Manager project metadata.

Enterprise Manager is a project, which like any other MSTR projects, consist of reports and schema object. This means that we can make add, edit, and modify these reports to suite our need. If you have not made any modifications to the Enterprise Manager project, such as creating new reports or altering existing report definitions, you can replace the previous version of the Enterprise Manager project with the new version of the project in Enterprise Manager. If you want to keep using your customized Enterprise Manager reports or other objects, you can simply update your Enterprise Manager project in the same way as all your other projects. If you want to take advantage of the new reporting capabilities in MicroStrategy 9.5.1, and want to keep using your custom Enterprise Manager objects, you can update your existing project, and then import the new reports and metrics from the MicroStrategy 9.5.1 project.

  • For more detailed information about the Enterprise Manager metadata upgrade process, see MicroStrategy Tech Note TN30304.

How can we upgrade and replace the Enterprise Manager project?

To replace your existing Enterprise Manager project with the MicroStrategy 9.5.1 project, install the new Enterprise Manager metadata in your metadata database, using the Enterprise Manager console and the Project Mover Wizard. If you do not perform the DML upgrade to the statistics tables and the data warehouse, Enterprise Manager cannot report on statistics collected prior to upgrading to MicroStrategy 9.5.1. To upgrade and replace the Enterprise Manager project:

  1. Launch Enterprise Manager console. From the Start menu, point to All Programs, then MicroStrategy Tools, then select Enterprise Manager Console. The Enterprise Manager Console opens.
  2. Select Initialize.
  3. Read and click Next. Read the Initialize Overview page. Be sure you know the Data Source Name for the Enterprise Manager metadata database before you continue. Click Next.
  4. Read and click Next. Read the Initialize Project page and click Transfer to import the project files. The Project Mover Wizard opens.
  5. Step through the Project Mover Wizard, entering the information for your system where prompted. For detailed instructions on each page of the wizard, click Help. On the Select Your Source Files page, make sure you clear the Warehouse Source check box, so that the Enterprise Manager data warehouse is not transferred.
  6. Review the information about the project transfer, and click Transfer when you are ready. The process can take several minutes. When the transfer process is complete, the Project Mover Wizard closes and you are returned to the Enterprise Manager Console.

How can we upgrade an existing Enterprise Manager project?

If you want to keep your existing Enterprise Manager project, and do not need access to the new functionality available in MicroStrategy 9.5.1, you can update your existing metadata in the same way as you update the other projects on your server. Follow the procedure below to update your existing Enterprise Manager project:

  1. Connect to the Enterprise Manager project using Developer. In Developer, log in to the Enterprise Manager project. You must use a login that has administrative privileges. A dialog box with update options is displayed.
  2. Select the Update Report Services document definitions and Update report definitions check boxes.
  3. Click Yes to proceed with the project updates.
  4. Restart the Intelligence Server.

How can we take advantage of new reports that had been added to the latest version of Enterprise Manager?

You may have created custom objects in Enterprise Manager that you want to keep, and also want to take advantages of the new reporting features in Enterprise Manager. You can do this by updating your existing Enterprise Manager project, and then using Object Manager to migrate the new and updated objects from the new Enterprise Manager project into your existing project. If you do not perform the DML upgrade to the statistics tables and the data warehouse, Enterprise Manager is not able to use the new reporting features on statistics collected prior to upgrading to MicroStrategy 9.5.1. To update your custom Enterprise Manager environment with the new features:

  1. Update your existing Enterprise Manager project (ignore the new features for now)
  2. Make a backup of your Enterprise Manager project using the Project Duplication Wizard.
  3. Identify the difference. Use Object Manager’s project comparison feature to identify which objects are different between the MicroStrategy 9.5.1 project and your existing project. The MicroStrategy 9.5.1 project is located in the Microsoft Access database EM_PROJ_MD.mdb, in the Enterprise Manager directory. By default, this directory is C:\Program Files\MicroStrategy\Enterprise Manager.
  4. Migrate the new objects from the latest version to your existing project. Use Object Manager to migrate the new objects from the MicroStrategy 9.5.1 project to your existing project. Specify the EM_PROJ_MD.mdb file as the source project, and your Enterprise Manager project as the destination project.

How can we initialize the Enterprise Manager production environment?

The Enterprise Manager metadata and data warehouse that are installed with Enterprise Manager are in Microsoft Access databases. To use them in a production environment, you need to import them into the Enterprise Manager databases that you created earlier. The metadata contains all the Enterprise Manager project definition information: schema objects, metrics, templates, filters, reports, and more. The data warehouse contains configuration tables necessary to the operation of Enterprise Manager, some time-based lookup tables, and standard lookup tables that are populated during the data load process. Initializing the environment also involves running a SQL script specific to the type of production database that you are using. This SQL script creates the lookup and fact tables and creates the primary keys in the data warehouse. It also inserts database-specific SQL procedures into the EM_SQL table for use in the data load process.

If problems occur with the initialization process, you can check the file EMProjectMover.log to help with troubleshooting. This file is located by default in C:\Program Files (x86)\MicroStrategy\Enterprise Manager. To initialize the Enterprise Manager project:

  1. Launch Enterprise Manager console. From the Windows Start menu, point to All Programs, then MicroStrategy Tools, and then select Enterprise Manager Console. The Enterprise Manager Console must be run with administrator privileges. If you are not an administrator on the local machine, from the Start menu, instead of selecting Enterprise Manager Console, right-click Enterprise Manager Console and select Run As Administrator.
  2. Read the Home page and click Next.
  3. Read the Initialize Overview page and Click Next. Be sure you have the Data Source Names for the Enterprise Manager data warehouse (the same database that you are using to log Intelligence Server statistics) and the Enterprise Manager metadata database before you continue.
  4. Read the Initialize Project page and click Transfer to import the project files. The Project Mover Wizard opens. This procedure walks you through the Project Mover Wizard. For a detailed explanation of the wizard, see the Help for the Project Mover Wizard (click Help).
  5. Read the welcome screen and click Next. The Select your source files page opens.
  6. Verify that the correct Metadata Repository Source is specified. The metadata repository source is a Microsoft Access database that was installed as part of the Enterprise Manager installation. If it is not in the default Enterprise Manager directory, search for EM_Proj_MD.mdb and type the correct path in the field.
  7. Verify that the correct Warehouse Source is specified. The warehouse source is also a Microsoft Access database that was installed as part of the Enterprise Manager installation. If it is not in the default Enterprise Manager directory, search for EM_WH.mdb and type the correct path in the field.
  8. Leave the Run a SQL script check box selected, and make sure that the Overwrite warehouse tables if they exist check box is selected.
  9. Click Next. The Project Selection page opens.
  10. Select Enterprise Manager and click Next. The Run a SQL Script on the Warehouse page opens.
  11. In the SQL script to be run after warehouse transfer field, specify the Enterprise Manager SQL script appropriate to your data warehouse:
    1. Click the browse (…) button. A window opens to a directory containing .sql files.
    2. Select the appropriate em_sql_databasetype.sql file for your Enterprise Manager data warehouse.
    3. Click Open.
  12. Click Next. The Metadata Repository Location page opens.
  13. Select the Data Source Name for the Enterprise Manager metadata database from the drop-down list.
  14. Type a valid User Name and Password for this database.
  15. Click Next. The Warehouse Location page opens.
  16. Select the Data Source Name for the Enterprise Manager data warehouse and statistics tables from the drop-down list.
  17. Type a valid User Name and Password for this database.
  18. Select the correct database type from the Database Connection Type drop-down list.
  19. Click Next. The Metadata Repository Connection page opens.
  20. Provide the name for the project source. In the Project Source Name field, type the name of the project source to create the Enterprise Manager project in. If this project source does not exist, it will be created.
  21. Click Next. The Summary page opens.
  22. Read and click Transfer. Review the information on the summary page and click Transfer when you are ready. The process can take several minutes.
  23. Click Next. When the transfer process is complete, the Project Mover Wizard closes and you are returned to the Enterprise Manager Console. Click Next. The Configure Overview page opens.

What are the steps?

Refer to What are the steps to setup Enterprise Manager for the very first time on the main Enterprise Manager page.

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License