It is tempting to try to use parent-child relationships to handle many-to-many relationships but Yukon has introduced a many-to-many relationship functionality that’s really cool.  For example, using a geography hierarchy noted below, France and Spain both belong to a hierarchy of "Western Europe" and "EU"   Western Europe        Switzerland (SZ)        France (FR)        Spain (SP)        Lithuania (LI) EU        France (FR)        Spain (SP)   And the problem with many-to-many relationships is that you risk double-counting, double-summing of in this scenario.  Well, to resolve this, you can use the reference of: http://www.sqljunkies.com/WebLog/sqlbi/archive/2004/10/04/4447.aspx   Instead of the above examples of Customer, Account and CustomerAccount; you would…

Often, you will want to get the top or bottom X number of dimension members based on the dimension hierarchy.  Within Analysis Services, you have the functions of TopCount, TopSum, and TopPercent (and the equivalent of Bottom functions) but these are based on a Measure.  And what you want is the top child or bottom child of a member based on the dimension order – not on the Measure order.   Well, to do this: withmember [Measures].[test] as ‘1’select {  [Measures].[My Count]} on columns, {    topcount(descendants([Domain].[Domain Hierarchy], 2, LEAVES), 1),    bottomcount(descendants([Domain].[Domain Hierarchy], 2, LEAVES), 1)} on rowsfrom [Cube] The trick for…