Is It Possible To Use Microstrategy Object Manager While Other Users

1.	Is It Possible To Use Microstrategy Object Manager While Other Users Are Making Changes In Microstrategy Agent?
Answer» Using MicroStrategy Object Manager to copy/move objects around is not recommended while other USER sessions are making CHANGES using MicroStrategy Agent, as it could lead to metadata inconsistency. PROJECT and schema locking PREVENT multiple USERS sessions from manipulating the schema at the same time. This prevents metadata inconsistency from occurring. Using MicroStrategy Object Manager to copy/move objects around is not recommended while other user sessions are making changes using MicroStrategy Agent, as it could lead to metadata inconsistency. Project and schema locking prevent multiple users sessions from manipulating the schema at the same time. This prevents metadata inconsistency from occurring.

Is It Possible To Use Microstrategy Object Manager While Other Users Are Making Changes In Microstrategy Agent?

Answer»

Using MicroStrategy Object Manager to copy/move objects around is not recommended while other USER sessions are making CHANGES using MicroStrategy Agent, as it could lead to metadata inconsistency. PROJECT and schema locking PREVENT multiple USERS sessions from manipulating the schema at the same time. This prevents metadata inconsistency from occurring.

Using MicroStrategy Object Manager to copy/move objects around is not recommended while other user sessions are making changes using MicroStrategy Agent, as it could lead to metadata inconsistency. Project and schema locking prevent multiple users sessions from manipulating the schema at the same time. This prevents metadata inconsistency from occurring.

Discussion

No Comment Found

Related InterviewSolutions

What Is A Materialized View?
How To Reduce Multiple Passes To One In A Report?
I Have A Fact Table At All Time Levels(date, Week...year). I Have The Similar Fact Table At Year Level. If I Create A Report With A Fact Attribute And A Metric Based On That Fact........ How Do We Force The Mstr To Use Year Level Fact Table Instead Of Using The All-levels Fact Table?
If We Need To Restrict Certain Columns From Appearing To A User/user-group How Can We Do It?
If We Need To Restrict Certain Rows From Appearing To A User/user-group How Can We Do It?
How Do We Prevent A Cross-join?
What Leads To A Cross-join Or How Does A Cross-join Occur?
When Do We Need To Create A View Or A Materialized View In A Database?
What Kind Of Optimizations You Did?
How Can Users Design Dashboards Quickly And Without Programming Experience Or Training?