Compression has in general the following advantages: BW on SAP HANA: Performance of InfoCube compression; SAP. What Is an Infocube in SAP BI/BW? How To Create One? What is Infocube? Infocube is data storage area in which we maintain data which we are extracting . Posts about Infocube Compression written by Rahul Sindhwani.
|Published (Last):||22 January 2004|
|PDF File Size:||14.67 Mb|
|ePub File Size:||19.60 Mb|
|Price:||Free* [*Free Regsitration Required]|
InfoCube Compression in SAP BI
When you load data into the InfoCube, entire requests can be added at the same time. Each of these requests has its own request ID, which is included in the fact table in the package dimension. This makes it possible to pay particular attention to individual requests. One advantage of the request ID concept is that you can subsequently delete complete requests from the InfoCube.
However, the request ID concept can also cause the same data record where all characteristics are the same except the request ID to appear infocubf than once in the fact table. This unnecessarily increases the volume of data and affects system performance when you analyze data, since each time you execute a query, the system has to perform aggregation using the request ID.
Compression in BW InfoCubes – SAP NetWeaver Business Warehouse – SCN Wiki
You can eliminate these disadvantages by compressing data and bringing data from different sqp together into one single request request ID 0.
This function is critical, since you cannot delete compressed data from the InfoCube using its request ID. You must be absolutely certain that the data loaded into the InfoCube is correct.
You can choose request IDs and release them to be compressed. You can schedule the function immediately or in the background.
SAP infocube compression tables
You can schedule compression as part of a process chain. Compressing one request takes approximately 2.
With non-cumulative InfoCubes, compression has an additional effect on query performance. With non-cumulative InfoCubes, the marker for non-cumulatives is also updated.
This means that less data has to be read for a non-cumulative query which reduces the response time. If you perform compression for a non-cumulative InfoCube, the compression time including the time to update the markers is about 5 ms infocubf data record.
If you are using an Oracle database as your database, you can also compression queries on the relevant InfoCube while compression is running. You can execute the query once compression is finished. If you do not want the InfoCube to contain entries with zero values for key figures in reverse posting for exampleyou can run zero-elimination at the same time as compression.
In this case, the entries where all key imfocube are equal to 0 are deleted from the fact table.
You cannot run zero-elimination for InfoCubes that contain non-cumulative values. For non-cumulative InfoCubes, you can ensure that the non-cumulative marker is not updated by setting the indicator No Marker Updating.
SAP BW – How to Compress InfoCube Data
If you are loading historic changes to non-cumulative values into an InfoCube after initialization has already taken place using the current non-cumulative, you have to use this option. If you do not use this option, the results produced in the query are incorrect. For performance reasons, you should compress subsequent delta requests. For performance reasons, and to save space on the memory, compress a request as soon as you have established that it is comrpession and is not to be removed from the InfoCube.
Features You can choose request IDs and release them to be compressed. Activities For performance reasons, and to save space on the memory, compress a request as comprfssion as you have established that it is correct and is not to be removed from the InfoCube.