SSAS Articles 
Design Analysis Services: Should you use many-to-many dimensions?
Design Analysis Services: Should you use many-to-many dimensions?
| Analysis Services: Should you use many-to-many dimensions? |
| Written by Denny Lee |
| Wednesday, 05 March 2008 11:51 |
| For starters, please note that I am not saying not to use many-to-many (m:n) dimensions in Analysis Services. This is an excellent feature that enables you to relate multiple leaf-level values to multiple parents. Many-to-many relationships are used heavily in many business scenarios ranging from sales to accounting to healthcare. But at times there may be query performance issues when dealing with a large number of many-to-many relationships and perceived accuracy issues. The purpose of this technical note is to provide background and logical business scenarios of how many-to-many dimensions work and their potential perceived accuracy issues. |
Latest Author Articles
- Reintroducing Usage-Based Optimization in SQL Server 2008 Analysis Services
- Analysis Services Distinct Count Optimization
- Analysis Services: Should you use many-to-many dimensions?
- Using ByAttribute or ByTable Processing Group Property with Analysis Services 2005
- Renaming an Analysis Services 2005 cube
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)
