| SSAS 2005: Cube Performance Tuning Lessons Learned |
| Written by Derek Comingore |
| Wednesday, 29 October 2008 00:21 |
|
A recent project has forced me (which is a good thing) to learn both the internals of SSAS 2005 as well as various performance tuning techniques to get maximum performance out of the OLAP server. It goes without saying that the grain of both your underlying data warehouse's Dimensions & Facts will drive how large your cubes are (total cube space). It also should be a given that Processing Time & Query (MDX) Execution Time usually compete with one another. Given the same grain of a model, the more Grain Data, Indexing, and Aggreggations you process upfront should generally result in a more performant end-user experience (but not always). And while ETL & Cube Processing time is of importance, in the real-world it is the end-user experience (capability and performance) which drives the DW/BI solution's adoption! Read more...
|
Tags: 2005, article, performance
Latest Author Articles
- SSAS 2005: Cube Performance Tuning Lessons Learned
- Value-Add: Data Warehousing & Analysis Services Cube Storage Estimates
- Cube Squared: Migrating Analysis Services to the SQL Server 2008 Platform, Part 1 of 2
- SSAS 2008 Upgrade Consideration: ODBC Data Sources from Analysis Services 2000 are not migrated
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)




