Strategy ONE

Aggregate Table Validation

Aggregate Table Validation is an advanced VLDB property that is hidden by default. For information on how to display this property, see Viewing and Changing Advanced VLDB Properties.

Reports that use aggregate tables are available for dynamic sourcing by default, but there are some data modeling conventions that should be considered when using dynamic sourcing.

In general, aggregate tables allow accurate data to be returned to reports from Intelligent Cubes through dynamic sourcing. However, if the aggregate tables use an aggregation other than Sum, or there is different data between aggregate tables and other tables in the data warehouse, this can cause aggregate tables to return incorrect data when dynamic sourcing is used. An example of an aggregate table not containing the same data is if an aggregate table includes data for years 2006, 2007, and 2008 but the lookup table for Year only includes data for 2007 and 2008.

You can enable and disable dynamic sourcing for aggregate tables by modifying the Aggregate Table Validation VLDB property. This VLDB property has the following options:

  • Aggregate tables contain the same data as corresponding detail tables and the aggregation function is SUM (default): This is the default option for aggregate tables, which enables aggregate tables for dynamic sourcing.
  • Aggregate tables contain either less data or more data than their corresponding detail tables and/or the aggregation function is not SUM: This option disables dynamic sourcing for aggregate tables. This setting should be used if your aggregate tables are not modeled to support dynamic sourcing. The use of an aggregation function other than Sum or the mismatch of data in your aggregate tables with the rest of your data warehouse can cause incorrect data to be returned to reports from Intelligent Cubes through dynamic sourcing.

You can disable dynamic sourcing individually for reports that use aggregate tables or you can disable dynamic sourcing for all reports that use aggregate tables within a project. While the definition of the VLDB property at the project level defines a default for all reports in the project, any modifications at the report level take precedence over the project level definition. For information on defining a project-wide dynamic sourcing strategy, see the In-memory Analytics Help.

Levels at Which You Can Set This

Project, report, and template