MicroStrategy ScanMD

Other Articles:

MicroStrategy ScanMD

Share on linkedin
LinkedIn
Share on facebook
Facebook
Share on twitter
Twitter
Share on whatsapp
WhatsApp

Welcome to this new #BestInMicro article! This is a space where I will be writing about different topics related to MicroStrategy, its use, best practices, and functionalities to get the most out of the tool.

Today we will be talking aboutScanMDIf not handled with caution, this tool can cause many more problems than it fixes. That is why today I will tell you what it is used for, and what are my recommendations when using it.

MicroStrategy-ScanMD-1

First things first: What is this ScanMD? What is it used for? why is there so much risk when using it?

ScanMD is a tool used to correct inconsistencies in the Metadata, i.e. inconsistencies in the definition of schema objects.

There are situations where, after modifying schema objects, transporting packages, updating tables, facts, or perhaps even the database itself, certain inconsistencies may be found (such as, for example, an invoice pointing to two different tables appearing as a duplicate invoice).

However, this is not a tool to be used regularly. Quite the opposite. Let’s remember that metadata is the foundation of our entire environment. With this tool, modifications are being made and the metadata is being “touched and restructured”. If for any reason in the use of ScanMD you modify something that you should not, you can completely corrupt the environment, and this is why ScanMD should be used only when the inconsistencies have been detected, understood and, whenever possible, verified with MicroStrategy support..

Here are some tips to keep in mind.

  • Make a Metadata Backup. Without it, there will be no way back in case of inconveniences.
  • Make sure you are using the correct version of ScanMD (as it has changed in versions 10.3 and 2019).
  • Ensure that there is a two-layer connection to the metadata to be analyzed.
  • There is no Metadata lock (caused by an editor or object manager).
  • Stop the Intelligence server, or at least have the project unloaded at the time of scanning.
  • Define a list of key reports, and validate that they work correctly. Using integrity manager can be a quick and easy alternative.

3 different types of analysis can be done with ScanMD: Configuration, all projects, or by specific project.

MicroStrategy-ScanMD-2

Although I do not intend to go into detail on how to perform an analysis, it is important to know how to approach the problem. This allows us not only to reduce the risk but also the execution time and the impact of what we are actually correcting.

MicroStrategy-VLDB-2

If the configuration for a VLDB property is edited at the level of a particular object (be it a metric, template, project, etc.), any object above it in the VLDB hierarchy automatically takes the custom configuration as the inherited value.

Conclusions

Although the article at times seems a bit “apocalyptic”, ScanMD is a very useful tool indeed. I have used it several times, and except for some exceptions (which, thanks to following the steps mentioned above, there was no problem) it has solved problems generated, in that case, by the modification of names in the model tables between environments.

Espero que este artículo haya sido de utilidad y los salve de algún dolor de cabeza. Don’t be afraid to leave questions, comments, or ask for a topic that interests you.

Deja un comentario

Your email address will not be published. Required fields are marked *