Skip to main content Skip to complementary content

MicroStrategy 7.0 to 11.x / 2021 - Export

Availability-note AWS

Bridge Requirements

This bridge:
  • is only supported on Microsoft Windows.

  • requires the tool to be installed to access its SDK.

Bridge Specifications

Vendor MicroStrategy
Tool Name Intelligence Server
Tool Version 7.0 to 11.x / 2021
Tool Web Site http://www.microstrategy.com/
Supported Methodology [Business Intelligence] BI Design (RDBMS Source, Dimensional Target, Transformation Lineage) via COM API

SPECIFICATIONS
Tool: MicroStrategy / Intelligence Server version 7.0 to 11.x / 2021 via COM API
See http://www.microstrategy.com/
Metadata: [Business Intelligence] BI Design (RDBMS Source, Dimensional Target, Transformation Lineage)
Component: MicroStrategy version 11.2.0

OVERVIEW

REQUIREMENTS
The bridge relies on the MicroStrategy Intelligence Server COM API in order to export metadata. Therefore, MicroStrategy must be properly installed on the computer executing this bridge.

FREQUENTLY ASKED QUESTIONS
n/a

LIMITATIONS
Refer to the current general known limitations at MIMB Known Limitations or bundled in Documentation/ReadMe/MIMBKnownLimitations.html

Please note, MicroStrategy database corruption may be a problem for the proper function of this bridge. Such corruption may be reported in the MicroStrategy log file: C:\Program Files\Common Files\MicroStrategy\Log\DSSErrors.log. MicroStrategy support is aware of this issue and provides a ScanMD program which may be used to cleanup these errors. Be sure to always run the ScanMD program before using this bridge.

SUPPORT
Provide a troubleshooting package with debug log. Debug log can be set in the UI or in conf/conf.properties with MIR_LOG_LEVEL=6


Bridge Parameters

Parameter Name Description Type Values Default Scope
Version Select here the version of MicroStrategy you want to use. ENUMERATED
Auto detect
11.x
10.5 to 10.8
9.x to 10.4
8.0.0 to 8.1.2
7.5.2
7.5.0
7.0
Auto detect  
Login Project Source name Enter here the MicroStrategy Project Source name you are interested in connecting to.

A Project Source is a connection to a repository located on a local or remote Intelligence Server, which holds connectivity to a Data Warehouse, and contains a number of metadata Projects operating on this Data Warehouse.

The list of Project Sources accessible from this computer is stored in the Windows Registry.
If you wish to connect to a remote Intelligence Server that has not yet been registered on the local computer (a Project Source pointing to this Intelligence Server is not yet defined), please use the MicroStrategy software to create this Project Source beforehand.
STRING   MicroStrategy Tutorial (Direct) Mandatory
Login Project name Enter here the Project name you are interested in exporting to, for the chosen Project Source.

A project with this name will be created in the Intelligence Server designated by the Project Source option.
STRING   My new project Mandatory
Login user Enter here the user ID used to connect to the Project Source. STRING   Administrator Mandatory
Login password Enter here the password used to connect to the Project Source. PASSWORD      
Database Instance Name Please define a database Instance object pointing to your data warehouse before running this bridge.

For example you can create the Database Instance object using the Database Instance Wizard in the MicroStrategy Desktop application.

Once the Database Instance is created, it will be available in the 'Administration / Database Instance Manager' folder of the current Intelligence Server.

Specify in this option the name of the Database Instance to be used to connect to the data warehouse.
REPOSITORY_MODEL     Mandatory
Verbosity This parameter controls the dimensional modeling forward engineering verbosity level.

'False'
Normal verbosity.

'True'
Additional information is printed in the log.
BOOLEAN   True  

 

Bridge Mapping

Meta Integration Repository (MIR)
Metamodel
(based on the OMG CWM standard)
"MicroStrategy 7.0 to 11.x / 2021"
Metamodel
MicroStrategy
Mapping Comments
     
Attribute WarehouseColumn, Attribute, AttributeForm The physical name of the Column is used to reference the underlying database Column. The logical business name of the Column is used to create an Attribute or a Fact A default ID AttributeForm is created for each attribute
DesignLevel   Not applicable if LOGICAL_ONLY
Name Name  
PhysicalName Name if a business name has been set
Class WarehouseTable, LogicalTable The physical name of the Table is used to reference the underlying database Table and insert it into the Project Catalog The logical business name of the Table is used to create a LogicalTable in the Project Schema
Comment Comments  
DesignLevel   Not applicable if LOGICAL_ONLY
DimensionalRole   If set to Fact, Attributes and Facts will be created in the equivalent LogicalTable. If set to Dimension or Outrigger, Attributes only will be created in the equivalent LogicalTable,
Name Name  
PhysicalName Name if a business name has been set
DatabaseSchema Schema Used in the identification of the Warehouse Tables
Name name  
PhysicalName name  
Type   set to FACT if the logical table contains facts, REGULAR otherwise
UserDefined   set to TRUE
ForeignKey LogicalTable Lookup The foreign key is used to infer which LogicalTable to use in a lookup for an AttributeForm
SQLViewAttribute WarehouseColumn, Attribute Same algorithm as Class
Name Name  
PhysicalName Name if a business name has been set
SQLViewEntity WarehouseTable, LogicalTable The physical name of the View is used to reference the underlying database View and insert it into the Project Catalog. The logical business name of the View is used to create a LogicalTable in the Project Schema
Name Name  
PhysicalName Name if a business name has been set
StoreModel Project This bridge creates a new Project in the MicroStrategy Intelligence Server
Comment Comments  
Description Description  
Name Name  
NativeId ID MicroStrategy object ID

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!