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

KB36189: Changes to the dataload process in MicroStrategy Enterprise Manager 9.x for updating relationship tables in MicroStrategy Enterprise Manager warehouse.


Community Admin

• Strategy


Changes to the dataload process in MicroStrategy Enterprise Manager 9.x for updating relationship tables in MicroStrategy Enterprise Manager warehouse.

Introduction:
Strategy Enterprise Manager offers a dataload option 'Repopulate Relate Tables' that can be used to repopulate all the relate tables in the Strategy Enterprise Manager Warehouse
Behavior for updating relate tables in Strategy Enterprise Manager 9.x
Starting with Strategy Enterprise Manager 9.x, the regular dataload process updates all relate tables as per changes made to objects (objects which have a modification date that falls within the migration window). Considering the same example used in the previous section, if an existing document D1 is edited to remove one dataset R1, the relate table IS_REP_DOC is updated to remove the relation between document D1 and report R1. This update is performed even when the option 'Repopulate Relate Tables' is not checked. If SQL logging is enabled for the dataload process, it is seen that during a regular dataload, the relate tables are also modified. Logs similar to the following will be seen in the MSTRMigration.log. As seen from the logs below, if an object has a modification time that falls within the dataload window, information for that object is first deleted from the relate table and new information is populated. This logic for updating the relate tables is applicable to regular dataload and custom window dataload.
 
Sample Code/Error
4/11/2011 12:51:03 PM   Start moving Table IS_REP_DOC.
4/11/2011 12:51:03 PM   INSERT INTO EM_LOG VALUES (sysdate, 'Start moving Table IS_REP_DOC.')
4/11/2011 1:40:28 PM   SELECT IS_DOC_ID FROM IS_DOC WHERE IS_DOC_GUID = 'E918791C441387902DD5FEBCD74B1041' AND IS_PROJ_ID=1
4/11/2011 1:40:28 PM   DELETE FROM IS_REP_DOC WHERE IS_PROJ_ID=1 AND IS_DOC_ID=425
4/11/2011 1:40:28 PM   INSERT INTO IS_REP_DOC (IS_PROJ_ID, IS_DOC_ID, IS_REP_ID) SELECT 1, 425, B.IS_REP_ID FROM IS_REP B WHERE B.IS_REP_GUID IN ('D1AE588B11D5C4D04C200E8820504F4F')
4/11/2011 12:51:04 PM   End moving Table IS_REP_DOC.
4/11/2011 12:51:04 PM   INSERT INTO EM_LOG VALUES (sysdate, 'End moving Table IS_REP_DOC.')
 
Because of this behavior in Strategy Enterprise 9.x, it is not necessary to run the dataload option 'Repopulate Relate Tables' to synchronize the information in the relate tables with the metadata. Only if users find that some information is missing from some relate tables, it is necessary to run this option.
 


Comment

0 comments

Details

Knowledge Article

Published:

June 5, 2017

Last Updated:

June 5, 2017