Metadata Doctor (MD Doctor) in Microstrategy

Metadata Doctor (MD Doctor) is a utility that detects and fixes certain physical inconsistencies in MicroStrategy 9.4.x - 9.5.x metadatas that may prevent MicroStrategy 9.4.x - 9.5.x products from functioning correctly.

In simple terms, it detects physical inconsistencies by running SQL against different metadata tables and then comparing results. If an entry is found in one table but not in the main lookup table of the metadata then that denotes a physical inconsistency and MD Doctor will delete that orphan entry.

Note: MD Doctor is not a supported tool for MicroStrategy 10.x metadatas.

NOTE: MD Doctor should be used only after a metadata backup has been taken. MD Doctor should not be used repeatedly. It is meant to primarily serve as a quick-fix to physical inconsistencies and get environments up and running. If repeated use of MD Doctor is needed then a possible recurrent-metadata physical inconsistency is being encountered.

MSTR WARNING:

Manually editing values in the MSTR Metadata incorrectly may cause serious, project-wide problems that may make your project unusable. Since these are user-initiated changes, they are not covered by any MicroStrategy warranty. Users are strongly encouraged to backup the metadata prior to any alteration.

Pre-Requisites for using MD Doctor:

The following are pre-requisites for the use of MD Doctor:

MicroStrategy Developer 9.4.x - 9.5.x installed. The product and metadata versions should match exactly.
A Direct (2-tier) Project Source to the target Metadata.

MD Doctor Best Practices

Remember the following Best Practices when running MD Doctor:

Running MD Doctor should not be a routine operation. MD Doctor is meant to be used as a fix once Technical Support identifies that there is a metadata physical inconsistency causing an issue in the platform.
Before running MD Doctor (fix/scan mode), all operations against the metadata should be stopped.
Before running MD Doctor (fix mode), a backup of the metadata must be taken.
Always save the MD Doctor logs.

Using Metadata Doctor:

Run the setup.exe and follow installations instructions.
Go to the Start menu and look for the MD Doctor executable under MicroStrategy -> Tools
Select the Direct MicroStrategy data source which points to the metadata to be checked. If a direct data source to the metadata does not exist, use MicroStrategy Developer or MicroStrategy Configuration Wizard to create one before running this application.

Metadata Login-- Connection information to the actual metadata repository. Login and Table Prefix are read from the select Direct Datasource created through Desktop. The user must specify a password.

Data Source Login-- MicroStrategy login and password in order to be able to check the metadata translations table.
Select Detect and Fix options:
Detect only. Do not fix errors -- Also known as running MD Doctor in scan-mode.

Prompt me to fix errors-- Also known as running MD Doctor in fix-mode. Every time an error is encountered the user will be prompted to fix it. Used for targeted fixes.

Fix all errors automatically -- Also known as running MD Doctor in fix-mode. No prompts to the user when an error is encountered. Used for fixing all encountered inconsistencies.

IMPORTANT: Users should always backup their entire metadata before allowing Metadata Doctor to fix any inconsistencies.

Log File-- The location of the log file. MD Doctor produces a detailed log file that records metadata statistics, errors log and actions taken; moreover it can include the SQL run against the metadata when the Include SQL in log file option is enabled. By default, the log file is generated in the same directory where the MD Doctor executable resides. A new log is created each time MD Doctor is run, and the log file name has a timestamp of the corresponding execution.
Select the 'Start' button to begin. MD Doctor may be interrupted by clicking on the 'Stop' button. However, do not stop/interrupt MD Doctor while it is fixing inconsistencies in the metadata.
A Status window will appear to display the checks performed by MDf Doctor:

Comments

Export a Report Services document to Excel with formatting using URL API

Export a Report Services document to Excel with formatting using URL API in MSTR Web In order to export a document in excel format using the URL API, the executionMode must be set to 4. If excutionMode is not provided in the URL, by default PDF will be used as executionMode. Below are the list of parameters that the URL must contain in order to execute correctly. evt= 3069 src= Main.aspx.3069 executionMode= 4 documentID= 7E1644CA424F482DA811569FCE8127FF( Replace the document Id with your document ID) Sample URL for .NET environment: http://WebServerName/MicroStrategy/asp/Main.aspx?evt=3069&src=Main.aspx. 3069 &executionMode= 4 &documentID= 7E1644CA424F482DA811569FCE8127FF

Create an alert-based subscription in MicroStrategy Distribution Services

Create an alert-based subscription in MicroStrategy Distribution Services on Web Subscription to a report or Report Services document which will be executed when a certain conditional threshold is met based on another executing report. For example, a scheduled report executes which shows the Revenue by day for the past week. If the Revenue on any one day falls below a certain value, a subscription to another report or Report Services document can be triggered and delivered to a recipient. An alert based subscription can only be created directly on a report; however, another report or Report Services document can be delivered when the alert based subscription is triggered. Note: you need a grid report to create an alert and you cannot create if you want to create on a document with text boxes. The following example will walk through the basic steps on how to setup a subscription based on an alert like this: Follow the brief steps bel...

Configure a report for use with Bulk Export in MicroStrategy

Configure a report for use with Bulk Export in MicroStrategy The Bulk Export feature enables a large report to be saved as a delimited text file. Using this feature, it is possible to retrieve result sets from a large dataset without having to load the entire dataset into memory. PS: Once a report is setup for bulk export it cannot be used as a regular report. So if the report needs to be run as a normal report and as a bulk export report, the first step is to make a copy of the report for use with bulk export. Configure Bulk Export Bulk Export options are only available in MicroStrategy Developer. Open a 3-tier connection using MicroStrategy Developer and edit the desired report. Go to 'Data' on the top menu bar. Select 'Configure Bulk Export': Specify any additional desired configuration options. General Settings Bulk export database instance : This is the database instance to use to store the bulk export results. Temporary tables w...

Microstrategy "Error type: Odbc error. Odbc operation attempted

"Error type: Odbc error. Odbc operation attempted: SQLExecDirect. [HYT00:0: on SQLHANDLE] [MicroStrategy][ODBC Oracle Wire Protocol driver]Timeout expired" is shown when executing reports from Web When users are trying to execute some reports in MicroStrategy web in particular, they may receive the Error “SQL Generation Complete Index out of range” and “Timeout expired” error as shown below: Possible Causes: One possible cause is that the MicroStrategy Intelligence Server using a cached database connection that was already dropped by the RDBMS. To resolve this: Admin should delete the database connection caches and create a new DSNs in case they are sharing DSNs to connect to different databases. In addition, change the settings for the ‘Connection lifetime’ and the ‘Connection idle time out’. Follow the steps below to perform the mentioned changes and verify the report after each step and some of the settings require i-server r...

Microstrategy Dossiers explained

Microstrategy Dossiers With the release of MicroStrategy 10.9, we’ve taken a leap forward in our dashboarding capabilities by simplifying the user experience, adding storytelling, and collaboration.MSTR has evolved dashboards to the point that they are more than dashboards - they are interactive, collaborative analytic stories . Ultimately, it was time to go beyond dashboards, both in concept and in name, and so the've renamed VI dashboards to ‘ dossiers ’. Dossiers can be created by using the new Desktop product or Workstation or simply from the Web interface which replaces Visual Insights. All the existing visual Insights dashboards will be converted to Dossiers With MicroStrategy 10.9, there was an active focus on making it easier to build dashboards for the widest audience of end users. To achieve this, some key new capabilities were added that make it easier to author, read, interact and collaborate on dashboards ...

Stages in MicroStrategy Report Execution Process

Stages in MicroStrategy Report Execution Process The report execution is typically a 3 step process process of the below: Query Stage Populate & Evaluate Stage Cross-tab stage Query Stage: Retrieve data from the warehouse Populate & Evaluate Stage: Fill report data for display Cross-tab Stage: Pivot and display sorting and page-by

Microstrategy Alerts setup

Alerts Editor Alerts can be sent to an email address or to an iPhone, iPad, or Android device with MicroStrategy Mobile. This allows users to be notified of data that is likely to be important for making business decisions. You can also have formatting automatically applied to metric values in the report, to draw immediate attention to the data that meets the alert's threshold conditions. For example, when the Inventory Count data in a report falls below 1,000 units, you can have the report sent to you, with the values below 1,000 displayed in red text. You can specify a subject and message to display for the alert, as well as a report or document to be displayed when viewing the alert, as described below. You can receive and view alerts on a mobile device even if the MicroStrategy Mobile application is not running. Prerequisites You must have the MicroStrategy Distribution Services product installed and MicroStrategy Web must be configured to use Distribu...

Predictive modelling in Data Science using Microstrategy

Creating a predictive modelling in MicroStrategy MicroStrategy Data Mining Services has been evolving to include more data mining algorithms and functionality. One key feature is MicroStrategy Developer’s Training Metric Wizard. The Training Metric Wizard can be used to create several different types of predictive models including linear and exponential regression, logistic regression, decision tree, cluster, time series, and association rules. Linear and exponential regression The linear regression data mining technique should be familiar to you if you have ever tried to extrapolate or interpolate data, tried to find the line that best fits a series of data points, or used Microsoft Excel’s LINEST or LOGEST functions. Regression analyzes the relationship between several predictive inputs, or independent variables, and a dependent variable that is to be predicted. Regression finds the line that best fits the data, with a minimum of error. For example, you have a dataset ...

Images in Microstrategy PDF Export shows Red X

When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9.4.1 and 10.x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9.4.1 and 10.x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X" as shown below: However, the images in the report display properly when the report is executed in MicroStrategy Developer and Web. Furthermore, when the report is exported to PDF on Desktop (with the original images saved in WebASPX\Images), the images in the report display properly, as indicated below: CAUSE This is expected behavior. When the report is displayed in MicroStrategy Developer and Web, or when the report is exported to PDF from MicroStrategy Dev...

Microstrategy Custom number formatting symbols

Custom number formatting symbols If none of the built-in number formats meet your needs, you can create your own custom format in the Number tab of the Format Cells dialog box. Select Custom as the Category and create the format using the number format symbols listed in the table below. Each custom format can have up to four optional sections, one each for: Positive numbers Negative numbers Zeros Text Each section is optional. Separate the sections by semicolons, as shown in the example below: #,###;(#,###);0;"Error: Entry must be numeric" For more examples, see Custom number formatting examples . To jump to a section of the formatting symbol table, click one of the following: Numeric symbols Character/text symbols Date and time symbols Text color symbols Currency symbols Conditional symbols Numeric symbols For details on how numeric symbols apply to the Big Decimal data type, refer to the Project Design Guide . ...

Microstrategy Analytics

Search This Blog