Partitioning 
Partitioning
Use
By using partitioning you can split up the whole dataset for an InfoCube into several, smaller, physically independent and redundancy-free units. Thanks to this separation, performance is increased when reporting, or also when deleting data from the InfoCube.
Only certain database providers support this function (for example, ORACLE, INFORMIX). If you use a database that does not support this function, then this function is not provided by the BW system.
Prerequisites
You can only partition a dataset using one of the two partitioning criteria ‘calendar month’ (0CALMONTH) or ‘fiscal year/period (0FISCPER). At least one of the two InfoObjects must be contained in the InfoCube.
If you want to partition an InfoCube using the fiscal year/period (0FISCPER) characteristic, you have to set the fiscal year variant characteristic to constant.
See
Functions
When activating the InfoCube, the fact table is created on the database with one of the number of partitions corresponding to the value range. You can determine the value range yourself.
You choose the partitioning criterion 0CALMONTH and determine the value range
from 01.1998
to 12.2003
6 years * 12 months + 2 = 74 partitions are created (2 partitions for values that lay outside of the range, meaning < 01.1998 or >12.2003).
You can also determine how many partitions are created as a maximum on the database for the fact table of the InfoCube.
You choose the partitioning criterion 0CALMONTH and determine the value range
from 01.1998
to 12.2003
You choose 30 as the maximum number of partitions.
Resulting from the value range: 6 years * 12 calendar months + 2 marginal partitions (up to 01.1998, from 12.2003) = 74 single values.
The system groups three months at a time together in a partition (meaning that a partition corresponds to exactly one quarter); In this way, 6 years * 4 partitions/year + 2 marginal partitions = 26 partitions are created on the database.
Activities
In the InfoCube maintenance choose Extras à Partitioning, and specify the value range. Where necessary, limit the maximum number of partitions. Note that the value range can only be changed if there is no data contained in the InfoCube.