SSAS Articles 
Performance Tuning Loading Aggregate Data in Yukon 2005 (By Richard Tkachuk)
Performance Tuning Loading Aggregate Data in Yukon 2005 (By Richard Tkachuk)
| Loading Aggregate Data in Yukon 2005 (By Richard Tkachuk) |
| Written by Richard Tkachuk |
| Saturday, 19 May 2007 19:01 |
|
In some cases, the source data is pre-aggregated in one, some or all dimensions. In the simplest example, employee salary is loaded to all employees. Because a manager’s salary is not the aggregate of his reports, it should not be aggregated up the employee dimension. There are several other such examples. This document discusses how pre-aggregated data can be loaded directly into Analysis Services 2005. Note: the approach described here applies only to Analysis Services 2005 and not earlier releases. |
Tags: 2005, article, performance
Latest Author Articles
- MDX Performance Hits - v2
- Handling Begin and End Times in SQL Server Analysis Services 2008
- IIF Function Query Hints in SQL Server Analysis Services 2008
- Richard Tkachuk discusses the SQL CAT team, working with Analysis Services
- Querying Dimension Members In Analysis Services
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)
