Limit the number of aggregation designs in a measure group to three
This rule analyzes aggregation designs to determine whether there are too many aggregation designs.
For best performance, you should typically avoid having too many aggregation designs. It is usually not necessary, nor is it desirable from a management perspective, to create separate aggregation designs for every partition. Instead, partitions with similar size and usage can share the same aggregation designs. Three aggregation designs per measure group is generally sufficient.
For more information about how to design aggregations, see Designing Partition Storage and Aggregations in SQL Server Books Online.
For performance issues related to aggregations, partitions, and multiple aggregation designs, see the section, "Aggregation considerations for multiple partitions," in the SQL Server 2005 Analysis Services Performance Guide.