MicroStrategy ONE

Relationship Tables

Table Name Function

IS_ATT_ATT_FORM

Relationship table between Attribute and Attribute Form.

IS_ATT_HIER

Relationship table between Attribute and Hierarchy.

IS_COL_TABLE

Relationship table between Column and Table.

IS_MET_TEMP

Relationship table between Metric and Template.

IS_REP_ATT

Relationship table for reports and component attributes.

IS_REP_CONS

Relationship table between Consolidation and Report.

IS_REP_DOC

Relationship table between Report and Document.

IS_REP_FILT

Relationship table between Filter and Report.

IS_REP_MET

Relationship table for reports and component metrics.

IS_REP_PROMPT

Relationship table between Prompt and Report.

IS_REP_TEMPLATE

Relationship table between Template and Report.

IS_SCHED_REL_DOC

Relationship table for schedules and associated documents.

IS_SCHED_RELATE

Relationship table for schedules and associated reports.

IS_TABLE_FACT

Relationship table between Table and Fact.

IS_TEMP_ATT

Relationship table between Template and Attribute.

IS_USER_PROJ_SF

Relationship table for users and associated security filters.

IS_USR_GP_USER

Relationship table between User and User Group.

IS_USR_GP_USR_GP

Relationship table between User Group and User Group (Parent).

Enterprise Manager Metadata Tables

The following is a description of Enterprise Manager metadata tables.

Table Name Function

EM_COMP

Defines all MicroStrategy components being monitored. The abbreviation specifies the prefix used on tables relevant to the component. When a new component is added to the MicroStrategy product line, it can be entered in this table for monitoring.

Examples: Intelligence Server, Narrowcast Server

EM_IS_LAST_UPDATE

Provides the Data Loading process with a working window that identifies the period during which data should be moved into production area tables.

EM_ITEM

Defines all items in each component of the MicroStrategy product line being monitored. When a new item is added to a component, it can be entered in this table for monitoring, without any change to the migration code. This table also specifies the item's object type according to server and the abbreviation used in the lookup table name.

Examples: Report, Server Definition, User

EM_ITEM_PROPS

Identifies properties being tracked on a given item for a given component.

Examples: Attribute Number of Parents, Hierarchy Drill Enabled

Primary key: EM_COMP_ID, EM_ITEM_ID, EM_PROP_ID

EM_LOG

Stores logging information for Enterprise Manager data loads. The logging option is enabled from the Enterprise Manager console, Tools menu, Options selection.

Data warehouse purges are not logged in this table.

EM_PROPS

Shows properties of the Enterprise Manager application (for example: which projects and servers are being tracked).

EM_RELATE_ITEM

Contains a list of many-to-many relationship tables and the MicroStrategy items they relate.

EM_SQL

Provides the SQL necessary to insert, update, and delete a row from the lookup item table once the necessary information from the component API is available. If the SQL must be changed, make the change in this table (no changes in the code are necessary). This table also provides the SQL used to transform the logged statistics into the lookup tables.

Example: SQL statements to insert an attribute into the lookup attribute table in SQL Server