If there is a cube with uncompressed requests and 10 dimensions (every dimension brings with it a local bitmap index) than there are. step-by-step process to create Re-Partitioning of Info Cube in SAP-BI. (1). students. Created by KUNCHAM Software Solutions Pvt Ltd. Last updated 4/. Sap BW Info cube partitioning. 1. Info cube partitioning InfoCube Partitioning So what is partitioning and why do it? You use partitioning to.
|Published (Last):||10 December 2004|
|PDF File Size:||9.46 Mb|
|ePub File Size:||17.48 Mb|
|Price:||Free* [*Free Regsitration Required]|
You use partitioning to split the total dataset for an InfoProvider into several, smaller, physically independent and redundancy-free units.
This separation improves system performance when you analyze data delete data from the InfoProvider. If you are using this database you can also partition PSA padtitioning.
SAP Note includes more comprehensive information on this. At least one of the two InfoObjects must be contained in the InfoProvider. When you activate the Partitioniing, the system creates the table on the database with one of the number of partitions corresponding to the value range.
You can infocbe the value range yourself. You can also determine the maximum number of partitions created on the database for this table. Choose 30 as the maximum number of partitions.
Partitioning mechanism on an Infocube – SAP NetWeaver Business Warehouse – SCN Wiki
Resulting from the value range: The performance gain is only achieved for the partitioned InfoProvider if the time characteristics of the Partitioningg are consistent. In the following example, only record 1 is consistent.
Records 2 and 3 are not consistent: Note that you can only change the value range when the InfoProvider does not contain data. If data has already been loaded to the InfoProvider, you have to perform repartitioning. For more information, see Repartitioning. This means that you should not create partitions that are too large or too small.
Partitioning (SAP Library – Business Intelligence)
If you choose a time period that is too small, the partitions are too large. If you choose a time period that ranges too far into the future, the number of partitions is too great. Therefore we recommend that you create a partition for a year, for example, and that you repartition the InfoProvider after this time.
Where necessary, limit the maximum number of partitions. Features When you activate the InfoProvider, the system creates the table on the database with one of the number of partitions corresponding to the value range.