Partitioning

Use

You can use partitioning to divide the entire dataset of an InfoProvider into several smaller units that are independent and redundancy-free. This separation can improve performance during the data analysis or when deleting data from the InfoProvider.

Prerequisites

With DataStore objects, characteristics 0FISCPER and 0CALMONTH must be in the key in order to enable partitioning.

You can only implement the partitioning process by using one of the two partitioning criteria, Calendar Month (0CALMONTH) or Fiscal Year/Period (0FISCPER). For InfoCubes, partitioning by calendar week (0CALWEEK) is also supported. The InfoProvider must contain at least one of these InfoObjects.

Integration

Partitioning is supported by the following databases:

SAP HANA database: only for standard InfoCubes; the partitioning is fully specified by the system for SAP HANA-optimized InfoCubes.
IBM Db2 for z/OS
IBM Db2 for i
Oracle
Microsoft SQL Server

To improve the performance of IBM Db2 for Linux, UNIX and Windows, you can use clustering.

If using IBM Db2 for i as your database platform, you need a database version of at least V5R3M0 and need to have component Db2 Multi Systems installed. If using this database, you can also partition PSA tables. You first need to activate this function using RSADMIN parameter DB4_PSA_PARTITIONING = 'X' . For more information see SAP Note 815186 Information published on SAP site . If you use the export/import procedure to create a homogeneous system copy of BW systems with active partitioning, see SAP Notes 744735 and 782993 for IBM Db2 for i. In the case of a homogeneous system copy with the SAVLIB/RSTLIB procedure, no particular steps have to be performed. For more information about performing the system copy, see SAP Note 585277 Information published on SAP site .

Key Features

When you activate the InfoProvider, the table is saved to the database, with a number of partitions that corresponds to the value area. You can define the value area yourself.

You can also define the maximum number of partitions that can be created for this table on the database.

This only improves performance if the time InfoProvider's time characteristics are consistent however. In the case of partitioning with 0CALMONTH, this means that all values in a data record's 0CAL* characteristics have to match each other.

Make sure that the value area can only be changed if the InfoProvider does not contain any data. If data has already been loaded to the InfoProvider, you need to repartition.

More information: Repartitioning

Activities

In InfoProvider maintenance, choose Start of the navigation path Extras Next navigation step DB Performance Partitioning End of the navigation path and define the value area. If necessary, set the maximum number of partitions.