This project has moved. For the latest updates, please go here.

Aggregation Manager

This page has been moved to GitHub and can be found here.

Microsoft provides an Aggregation Manager sample application which gives an advanced interface for manually editing aggregations. We have taken this sample code and integrated it into BIDS Helper. This way, it can be run from Visual Studio when you're designing your cube, and aggregations you edit will be saved into your source code for the cube. (If you prefer, you can run the BIDS Helper version of Aggregation Manager live against a deployed cube if you open it through File... Open... Analysis Services Database.)

A number of bug fixes and enhancements were coded. Look at the complete list if you're interested. It also contains a few completely new features: Delete Unused Aggregations, Validate Aggregations, Printer Friendly Aggregations, and Similar Aggregations.

To use Aggregation Manager, right click on the cube in Solution Explorer:


Then you are given windows which allow you to edit aggregations manually:


Appendix C of the performance guide provides documentation on how to use Aggregation Manager. The UI of Aggregation Manager inside BIDS is only slightly different in a few places.

Aggregation Manager can also be launched from the Partition tab of the cube designer:

After completing your edits to aggregations using Aggregation Manager, you can deploy your changes using the Deploy Aggregation Designs feature. That feature will deploy all changes made in Aggregation Manager except the assignment of aggregation designs to particular partitions.

The instantaneous aggregation size estimate (which shows at the top of the screen) does as good a job as is possible estimating the size based upon the EstimatedCount of dimension attributes, the EstimatedRows of the measure group, and the number of dimension keys included in the aggregation. (If the EstimatedCount/EstimatedRows properties are not set or are not up to date, then use the Update Estimated Counts feature.) When it shows a range of estimated sizes, the uncertainty is due to the unknown sparsity when you crossjoin multiple dimensions. For exact aggregation sizes, deploy the aggregation design, run ProcessIndex, then use the Physical Aggregation Sizes screen which can be opened via the context menu of an individual partition in Agg Manager.

Last edited Oct 1 at 3:03 AM by furmangg, version 13