InfoCube Performance 

Use

Here you can find the options that allow you to affect not only the load performance but also the query performance.

Functions

Database Indexes

With an increasing number of data records in the InfoCube, not only the load but also the query performance can be reduced. This is attributed to the increasing demands on the system for maintaining indexes. The indexes that are created in the fact table for each dimension allow you to easily find and select the data. You should not create indexes when initially loading data into the InfoCube. Create the indexes after you have created the InfoCube.

The indexes displayed are the secondary indexes of the F and E fact tables for the InfoCube. The primary indexes and those defined by the user are not displayed. The aggregates area deals with the corresponding indexes of the fact table for all aggregates of an InfoCube.

Checking Indexes

Using the pushbutton Check indexes, you can check whether indexes already exist, and whether these existing indexes are of the correct type (bitmap indexes).

Yellow status display: There are indexes of the wrong category

Red status display: No indexes exist, or one or more indexes are faulty

You can also list missing indexes using transaction DB02, pushbutton Missing Indexes. If a lot of indexes are missing, it can be useful to run the ABAP reports SAP_UPDATE_DBDIFF and SAP_INFOCUBE_INDEXES_REPAIR.

Deleting Indexes

For delta uploads with a large quantity of data (more than a million records), you should not align the database indexes of the InfoCube with every roll up, rather delete the indexes first, and then completely reconstruct them after rolling up.

Repairing Indexes

Using this function you can create missing indexes or regenerate deleted indexes. Faulty indexes are corrected.

Aggregate Table Indexes

Just as for the indexes of the fact table, you can maintain the indexes of the aggregation tables. Maintaining the indexes of the aggregation tables affects all the aggregation tables of the InfoCube.

If the InfoCube contains more than 50 million records, you should, as a rule, refrain from deleting and recreating indexes.

Database Statistics

Database statistics are used by the system to optimize the query performance. You should keep the database statistics up-to-date for this reason.

It is recommended that you always update the statistics if you have loaded more than a million new records in the InfoCube since the last update.

Using the pushbutton Check statistics, you can check the InfoCube to see if statistics exist. If no statistics exist yet, the status display changes to red. Using Recalculate statistics, you can add the missing InfoCube statistics in the background.

You can determine the percentage of InfoCube data, that is used for creating the statistics. The percentage is set to 10% by default. The larger the InfoCube, the smaller you should choose the percentage, since the demand on the system for creating the statistics increases with the change in size.

For up to 10 million entries in the InfoCube, you should set the percentage of InfoCube data used for creating the statistics to 100%.