Show TOC

Component documentationPerformance Optimization with Aggregates


Relational aggregates allow you to improve the performance of BEx queries when data is read from an InfoCube. The data of a BW InfoCube is saved in relational aggregates in an aggregated form. Relational aggregates are useful if you want to improve the performance of one or more specific BEx queries, or make specific improvements to reporting with characteristic hierarchies.

Recommendation Recommendation

In all other cases, if relational aggregates are not sufficient, are too complex, or have other disadvantages, we recommend that you use SAP NetWeaver BW Accelerator (see SAP NetWeaver BW Accelerator).

End of the recommendation.

Caution Caution

Note that the system does not support using aggregates if you use your BW system with the SAP HANA database. The reason for this is that using aggregates would not improve performance in this scenario (see Analytic Engine).

End of the caution.


Accessing the OLAP Processor

You can use relational aggregates and a BW Accelerator index for the same InfoCube. A BEx query always tries to use performance-optimized sources by checking the sources from which it can draw the requested data. It checks the sources in the following order:

  1. OLAP cache

  2. BW Accelerator index

  3. Relational aggregates from the database

  4. InfoCubes from the database

If an active BW Accelerator index exists, the OLAP processor always accesses this BW Accelerator index and not the relational aggregates. Therefore, with regard to modeling, we recommend that you create either relational aggregates or a BW Accelerator index for an InfoCube.

Query Execution

When the query is executed, it is clear to the user whether data is being read from an aggregate, a BW Accelerator index, or an InfoCube.

In the maintenance transaction, you can deactivate one or more aggregates on a temporary basis to test them for performance purposes or to analyze data consistency.

You can also execute the query in the Query Monitor (transaction RSRT) using a corresponding debug option and by choosing Execute + Debug (Execute + Debug). In the Debug Options dialog box, choose Do Not Use Aggregates to execute the query with an InfoCube if no BW Accelerator indexes exist.