Attribute Relationships in Analysis Services – RIGHT vs WRONG
Just a quick one – I just saw again that someone has built his attribute relationships wrong. And that is in SSAS 2008 even after there is a nice graphical interface to it. I believe it is wrong by design. To illustrate:
The dimension:
Current version (WRONG):
Desirable version (RIGHT):
It is not hard – you have:
One-to-Many Chart Names for a Version,
One-to-Many Ledger Names for a Chart Name, and
One-to-Many Finance Structures per Ledger Name.
They form a hierarchy, which has levels.
Each Finance Structure relates to a Ledger Name,
each Ledger Name relates to a Chart Name, and
each Chart Name relates to a Version.
Having the correct set-up allows Analysis Services to create aggregations correctly, so the cube performance is optimised and MDX queries run quicker. Also, if the aggregations are wrong we can sometimes get wrong results for our queries…
If you enjoyed this post, make sure you subscribe to my RSS feed!
Related posts:
- When Not To Write MDX and When Not To Use Analysis Services
- Average Aggregation in Analysis Services
- 7 Ways to Process Analysis Services Objects
Loading ...