Management Misleading partition row count in Aggregation Design Wizard when measure group is at a higher level than its source granularity
| Misleading partition row count in Aggregation Design Wizard when measure group is at a higher level than its source granularity |
| Written by Shabnam Watson |
| Monday, 25 August 2008 03:01 |
|
Problem I was recently analyzing a MDX query for its performance. I realized that the query was hitting more than one partition even though the query had a monthly slice specified and the measure group was partitioned by month using a date key. The Date key was a smart key and did not overlap between monthly partitions. After further investigation, I found out that the respective partitions did not have any indexes built no matter how I processed them. This was true even after a full process. The estimated row counts and the dimension attribute counts were all specified. The partition row count was way over the minimum limit of 4096 rows. The source table had close to 3 million rows for each month. Read more...Misleading partition row count in Aggregation Design Wizard when measure group is at a higher level than its source granularity |
Tags: 2005, article, partition
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)
