| Parent Child Attribute performance woes in SQL Server 2005 SP2: A case study |
| Written by Ajit Singh |
| Wednesday, 23 April 2008 00:26 |
|
Objective: To understand why Parent Child attribute perform so bad vis-a-vis level based hierarchies. Also, the parent child attribute in SQL server 2005 SP2 performs much worse than SQL server 2000 SP4. The total number of fact table rows are very small (100 to be precise). Note: the needed files to recreate the cubes and database are provided at the end of the blog. Read more... |
Latest Author Articles
- Fact table design for "State Workflow Analysis": Analysis Services Dimensional modeling
- NextAnalytics and MDX : Part 1 - Swap Cells with Row Labels
- Aggregate(), Sum() functions using calculated members does not work in Analysis Services 2005 SP2 (9.00.3042.00 version) but works in Analysis Services 2000 SP4
- Identifying intra-dimensional members relationship and reducing cube sparsity in Analysis Services 2005 SP2 : Cube design tip
- Code : utility code for converting cellset to a data table
Top Rated
- SSAS Implementation Best Practices slides in PDF format
- SSRS Report Against a SSAS Parent Hierarchy
- 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)
- SSAS Tutorial: SQL Server 2005 Analysis Services Tutorial by Accelebrate

