2. Update the Metadata

After upgrading the Intelligence Server, update the metadata by performing the procedure that follows. This procedure creates and updates metadata tables to support new features available in MicroStrategy ONE.

Updating the metadata ensure compatibility between your pre-existing objects and the MicroStrategy clients. You can also take advantage of new configuration settings exposed through the client applications, functionality, and objects available only with the updated version of metadata.

During the metadata update process, the Configuration Wizard generates additional SQL for tasks such as managing indexes and primary keys. To view this SQL during the update process, on the Summary Page of the Configuration Wizard, in the Summary pane, click SQL Preview. In addition, once you have completed the update process, the generated SQL is saved in the MicroStrategy common files directory. The file name is OriginalScript_generated.sql, where OriginalScript is the name of the original SQL update script. For example, if you are updating an Oracle database, the original SQL update script is mdorcl.sql and the generated SQL file is mdorcl_generated.sql.

As an alternative to stepping through each page of the Configuration Wizard for each project source that needs to be updated, you can create a response file with the update information and use that response file with the Configuration Wizard to automatically update your metadata. For more information about using a response file to update the metadata, see Using a Response File with Configuration Wizard.

If you do not have access to the GUI mode of Configuration Wizard, you must use a response file to update your metadata.

Prerequisites for Updating a MicroStrategy Metadata

Before attempting to update your MicroStrategy metadata to the latest version, make sure you meet the following prerequisites:

• The metadata update process can be executed only by a MicroStrategy user who is a member of the System Administrators user group. Having all administrative privileges is not sufficient: the user must be a member of the System Administrators user group.
• The project's metadata version from which you update must be older than, or the same as, the version of the product where Configuration Wizard is installed that will be performing the metadata update. An older version of the product is not able to perform an update on a newer version of metadata.
• The language settings of the client, project, and Intelligence Server must all be the same.
• The projects to be updated must not be locked. To unlock a project's metadata, in Developer, from the Administration menu, go to Locking > Unlock Project.
• Updating old metadata directly from version 10.0 or earlier to 11.3.1 or higher is not supported. You must move to an intermediate version first, than update to 11.3.1 or higher. The intermediate version should be between 10.0 and 11.3.

Metadata Update Process

If you attempt to update a project through the Configuration Wizard and the update fails, the project is locked. You must unlock the project before you attempt to upgrade the project again. To unlock a project, in Developer, from the Administration menu, go to Locking > Unlock Project.

To Make Metadata Updates Using the Configuration Wizard

1. Select the Upgrade existing environment to MicroStrategy Secure Enterprise option. Click Next.
2. Select the Intelligence Server components option. Click Next.
3. On the MicroStrategy Authentication page, type the username and password of a MicroStrategy system administrator. Click Next.

4. On the metadata Connection page, enter the database password to access the MicroStrategy metadata. Click Next.

   The DSN and Login ID are provided based on the server configuration that you did previously.

5. On the Select Components page, select the check boxes for each Intelligence Server you want to upgrade.
6. Under each selected Intelligence Server, select the system components you want to upgrade:
   • Upgrade metadata repository: The metadata repository contains the definitions of your MicroStrategy applications and supporting objects. An upgrade of your metadata is required to provide support for all new and updated features in the most recent version of MicroStrategy.
   • Migrate History List messages: Select this check box to migrate your existing History List repository to a new format for improved search results, scalability, and performance. A file-based repository can be migrated to a database-based repository or a hybrid repository, and a database-based repository can be migrated to a hybrid repository.
     • If you select this check box, additional configuration options for this migration are provided later, on the History List Migration page. During the upgrade process this Intelligence Server and any other Intelligence Servers in the cluster are stopped and restarted.
     • If you are using a file-based History List repository and want to continue using that format, clear this check box. The repository is updated, but its format is not affected, when you restart the Intelligence Server after the upgrade.
     • If you are using a database-based or hybrid History List repository and want to continue using the same type of repository, see 2. Update the Metadata for information about upgrading the History List database.
7. Select each project you want to update. Only projects that are loaded on Intelligence Server can be updated. Project updates can include any of the following options:

   • Execute project logical upgrade: Updates the project to the most recent version of MicroStrategy. This option also updates the report, document, and dashboard definitions to improve the performance and reduce the memory usage and storage requirements of reports and documents that were created with a previous version of MicroStrategy.

     Be aware of the following:

     • If this update has already been completed, this option is named Re-execute project logical upgrade.
     • This upgrade is required to execute any additional project upgrade options.
     • Updated Report Services documents cannot be run in previous versions of MicroStrategy.
     • Depending on the number of reports and documents in the project, this update may take significant time.
8. Click Next.
9. If you selected the Migrate History List messages option, on the History List Target Database page, specify the necessary information for the History List database.
10. Click Next.
11. On the Summary page, review your upgrade choices and click Finish.