EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB47301: In MicroStrategy Enterprise Manager 10.x, what is the purpose of the IS_REPOSITORY_ID column


Community Admin

• Strategy


This technote explains the use of the IS_REPOSITORY_ID column in the Enterprise Manager warehouse in 10.x as well as 9.x

Starting with Strategy Enterprise Manager 9.0.0 a column named IS_REPOSITORY_ID is seen in the lookup tables for all Configuration objects.The same column has been added to all the fact tables in Strategy Enterprise Manager 9.x and 10.x. Also, a column named REPOSITORYID has been added to all Statistics tables in Strategy version 9.3.0 and above.
The purpose of this column is to differentiate metadatas i.e., different user environments that are being monitored on Strategy Enterprise Manager 10.x. For example, a user with name user1 and GUID XXXX can exist in the development metadata and production metadata. To allow administrators to associate a user/activity to a specific metadata, this column has been introduced.
The REPOSITORYID populated in the Statistics tables is a GUID value which is obtained from the metadata that is currently logging statistics. The REPOSITORYID is stored in the metadata as a property set.
In the Strategy Enterprise Manager warehouse, the lookup table for REPOSITORYIDs is the table EM_MD. The data in the IS_REPOSITORY_ID column are integer values associated to each REPOSITORYID as per the EM_MD table. Example data in the EM_MD table is shown below.
 

ka04W000000Of44QAC_0EM4400000029Ot.jpeg

 
A record exists in the EM_MD table for each distinct metadata which was monitored or being monitored on Strategy Enterprise Manager 9.x. Consider a Strategy Intelligence Server configured to point to a metadata MD1. MD1's REPOSITORYID is XXXX and the corresponding IS_REPOSITORY_ID is 1. When this Intelligence Server is being monitored on Strategy Enterprise Manager, only one entry is seen in the EM_MD table and all configuration object LU tables will just have IS_REPOSITORY_ID=1. Now, consider that the Strategy Intelligence Server is configured to point to MD2 and the project source is re-configured on Strategy Enterprise Manager console.  Since this is a new metadata, a new entry corresponding to this REPOSITORYID will be added to the EM_MD table and a corresponding IS_REPOSITORY_ID (integer) will be assigned. The previously made entries for IS_REPOSITORY_ID=1 are not deleted from any table because it corresponds to a metadata which was monitored at some point. 
The table EM_PROPS also records the REPOSITORYID of each metadata which is currently being monitored by Strategy Enterprise Manager 10.x data loader. This information is stored as a property corresponding to each monitored project source, as shown below.
 

ka04W000000Of44QAC_0EM4400000029Ow.jpeg

 
 
 


Comment

0 comments

Details

Knowledge Article

Published:

June 9, 2017

Last Updated:

June 9, 2017