What Is The Difference In The Way Microstrategy Handles Custom Group

1.	What Is The Difference In The Way Microstrategy Handles Custom Group And Consolidations? Any Advantage Of Using One Over The Other?
Answer» Custom GROUPS are handled at the database end where as CONSOLIDATIONS are handled at the Analytical Engine end. As a result the Consolidations are not an overhead for the database as there is a SINGLE pass in the query. On the other hand Custom Groups are an overhead on the database as they fire a separate SQL pass for EVERY Custom group ELEMENT. Custom Groups are handled at the database end where as Consolidations are handled at the Analytical Engine end. As a result the Consolidations are not an overhead for the database as there is a single pass in the query. On the other hand Custom Groups are an overhead on the database as they fire a separate SQL pass for every Custom group element.

What Is The Difference In The Way Microstrategy Handles Custom Group And Consolidations? Any Advantage Of Using One Over The Other?

Answer»

Custom GROUPS are handled at the database end where as CONSOLIDATIONS are handled at the Analytical Engine end. As a result the Consolidations are not an overhead for the database as there is a SINGLE pass in the query. On the other hand Custom Groups are an overhead on the database as they fire a separate SQL pass for EVERY Custom group ELEMENT.

Custom Groups are handled at the database end where as Consolidations are handled at the Analytical Engine end. As a result the Consolidations are not an overhead for the database as there is a single pass in the query. On the other hand Custom Groups are an overhead on the database as they fire a separate SQL pass for every Custom group element.

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?