Run Integrity and Performance Comparison Testing
Once a testing environment has been setup, the two most important tasks before upgrading begin: integrity testing using Integrity Manager, and performance testing using the new MicroStrategy Capacity Testing Tool.
Since MicroStrategy 11.0, administrators have the ability in Integrity Manager to perform data comparison testing for all content objects, including reports, Report Services Documents, and dossiers, providing the confidence that values will not changes from the current production environment to the next. In the future, SQL comparison will be available as well, to allow testing without warehouse execution that can save time and enterprise resources. Additionally, enhanced logging along with the Upgrade Analysis Dossier provides administrators the ability to quickly identify intentional engine changes that are causing mismatched results while performing comparison tests.
The MicroStrategy Capacity Testing Tool is not only used for tuning your system but is also essential for ensuring that there is no performance degradation. With its fast and powerful metadata-level searching capability, administrators can quickly execute comparative performance testing with two different versions of MicroStrategy, to ensure that MicroStrategy 2019 will provide better performance with no degradation. Not only will end-users see a faster response time, but administrators can do further capacity testing to take advantage of the additional resources that will be available, which the environment can be tuned for. For more information about capacity testing, read here.
Run application end-user functional testing
For the past eight feature releases, there have been new products including MicroStrategy Library, Platform Analytics, Workstation, and more with a plethora of new functionality to explore and integrate into your day-to-day usage to expand adoption. However, before upgrading it is important to ensure that existing workflows that are used before upgrading have not been broken, and additionally haven’t changed, whether by the user interface, renaming, or any other scenarios that could impact its current implementation. To best test, talk with different business groups to understand their current usage, and work with the architects of that content to ensure a smooth and seamless transition. While things may have changed, they were done for a planned reason.
Certify upgrade and cutover to new upgraded environment
After you have done your due diligence with the steps listed above, it’s time to ask yourself, am I ready to release MicroStrategy 2019 to my users? Questions that should help you make a go/no-go decision include but are not limited to: "Have my integrity and performance tests been positive without any blockers?", "Have my developers and power users signed off with their functional testing?", "Does my support team understand the GUI changes and new options that exist to answer questions that may come in from end-users?", etc. Every environment is unique, and therefore different considerations will be taken for everyone. However, at the very least, MicroStrategy encourages administrators to get sign-off from each of the managers in charge of development, testing, deployment, support, education, and customer experience to ensure that everyone is in alignment to ensure and unified transition. If you have questions or concerns, refer to the Upgrade Guide or contact MicroStrategy Technical Support to speak with an engineer.