MicroStrategy ONE

Upgrade Best Practices

Review the following recommendations to help ensure the success and stability of your MicroStrategy system and projects when upgrading to the latest version of MicroStrategy.

If you are currently on a version of MicroStrategy that is not supported to directly upgrade to MicroStrategy ONE, you must first upgrade to the earliest supported version.

  • The following versions of MicroStrategy are supported for upgrade directly to MicroStrategy ONE:

    MicroStrategy Version Support Status Upgrade Path/Steps

    Expired

    Support is expired. Reach out to Support for assistance on the appropriate upgrade path. See Support Lifecycle for more information.

    Supported

    Upgrade to the latest MicroStrategy version.
  • If you are currently on a version of that is not supported to directly upgrade to ONE, and are doing an in-place upgrade, do not uninstall the current version of MicroStrategy before upgrading. MicroStrategy recommends performing an over-install.
  • Review the Readme for a complete list of new products, new features, and updates in MicroStrategy.
  • Follow the upgrade order and recommendations outlined in this guide, in particular the The Upgrade Process Checklist. Always upgrade the Intelligence Server before upgrading client applications such as MicroStrategy Web, Mobile, Library, and Developer.
  • Create an upgrade test environment by duplicating your production environment and production metadata. Upgrade this test environment to validate the upgrade before using in your production environment. For guidelines on how to test your system, see Validating the Upgrade.

  • Never downgrade a machine from a newer version to an older version of MicroStrategy. It is not supported and can cause problems. Contact Tech Support if this has been accidentally done.

  • Avoid installing MicroStrategy products using virtual sessions on the host machine such as Windows Terminal Services. Always install MicroStrategy directly on the server machine's physical interface, or by using a remote connection tool (such as Microsoft Remote Desktop) that takes full control of the server machine's interface and creates an actual administrator session on the machine.
  • Shut down all MicroStrategy Intelligence Server nodes in a clustered environment before upgrading. For more information about clustering Intelligence Servers, see the Clustering chapter in the System Administration Help.
  • Ensure that all data types assigned in existing projects are supported in the current MicroStrategy version. If a project containing columns with unsupported data types is upgraded, the data types for those columns are assigned as "reserved," and proper data types are not assigned in temporary tables. This affects report execution. Please see the Project Design Guide for a listing of the supported data types for each database type and additional information about changing to supported data types.