SSAS Articles 
Design DefaultMember, subcubes and non-aggregatable attributes
Design DefaultMember, subcubes and non-aggregatable attributes
| DefaultMember, subcubes and non-aggregatable attributes |
| Written by Marco Russo |
| Monday, 01 October 2007 16:39 |
|
Today I discovered that DefaultMember might result in a member other thant the default dimension member. Reading documentation, I got the idea that DefaultMember would be always the default member defined for a dimension into a cube. In reality, the default member could change into a subcube that excludes the original default member from a calculation. This is important because writing MDX Scripts you cannot anticipate any possible use of your cube... and you should carefully consider when DefaultMember is the real appropriate syntax on a case-by-case basis. You have to be particularly careful whenever you use DefaultMember on a non-aggregatable attribute. Let's look an example. |
Top Rated
- SSAS Implementation Best Practices slides in PDF format
- SSRS Report Against a SSAS Parent Hierarchy
- Using AS Data Mining to Add Forecast Values to a Cube
- Handling inter-dimensional members dependency and reducing cube sparsity using reference dimensions in Analysis Services 2005
- Cube structure optimization for MDX query performance in Analysis Services 2005 SP2: Tips for Parent Child Hierarchies usage
- Handling Multiple Calendars with a M2M Scenario
- Passing MDX parameters in Reporting Services reports
- Using UserName to Control Data Access and Default Member in SSAS 2K5 (Carrie Williams)
