Effects of Deactivating Different Types of Aggregates

• Demand-Defined Aggregate:

  If you deactivate an instance of a Demand-Defined aggregate, no new instances of the corresponding aggregate definition will be built unless a subsequent query causes the Aggregate Predictor to request that it should be reactivated.

• Prediction-Defined Aggregate:

  If you deactivate an instance of a Prediction-Defined aggregate, that aggregate could become active again (possibly with a new instance) after the next time the Project is published, when the Aggregate Predictor will re-run its prediction algorithm.

• User-Defined:

  If you deactivate an instance User-Defined aggregate (which includes hinted aggregates for a query dataset), that aggregate will get reactivated with a new instance following the next aggregate batch rebuild. Aggregate rebuilds can be triggered manually, by setting a trigger file, or automatically scheduled through the Design Center UI to rebuild at certain times.