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):||2 October 2013|
|PDF File Size:||12.16 Mb|
|ePub File Size:||8.96 Mb|
|Price:||Free* [*Free Regsitration Required]|
Once the data has been compressed, some functions are no longer available for this data for example, it is not possible to delete the data for a specific request ID. With non-cumulative InfoCubes, compression has an additional effect on query performance.
Infocube Compression | SAP BW Overview
SAP Note Too many compreasion request f table partitions. You can choose request IDs and release them to be compressed. October 10, 2 minute read. Compressing the fact table is one option that optimized the access to basis infocubes.
October 11, at 7: Martin Grob Post author. Comments Leave a Comment Categories Uncategorized. April 26, at 6: If you do not use this option, the results produced in the query are incorrect.
SAP infocube compression tables
If you are loading historic changes to non-cumulative values into an InfoCube after initialization has already infovube place using the current non-cumulative, you have to use this option.
Conclusion There are a couple of advantages and disadvantages compressing an InfoCube or not. Can I kill a compression? This makes it possible to pay particular attention to individual requests. Hi Martin, Comprdssion document. October 11, at 6: Those packages do not allow an aggregation and therefore each datapackage is limited within those boundaries.
Secondary Index usually abap tablesBitmap Index Bitmap indexes are created by default on each dimension column of a fact tableand B-Tree Index. Create a free website or blog at WordPress.
Can cube compression be compresion in a way, that reporting stays available while it is executed? Doing a compression can have an impact on the daily business and also affects reporting during this time.
Improve performance – by compressing the fact table #SAP #BW
To achieve this each InfoCube consist out of two two fact tables one with a request id and one without it. Compressed E-Fact table — Compression cannot be undone and individual requests cannot compgession differentiated anymore. Therefore compression is done best during non-reporting hours or weekends. Yes, you can kill the compression. This means that less data has to be read for a non-cumulative query which reduces the response time. Any requests fully compressed up to now will remain compressed.
Purpose To explain the concept and reasons behind compressing requests in InfoCubes Overview InfoCubes should be compressed regularly. Depending on the datamodel of the InfoCube and the frequency of loads as well as the content of the loaded data this can have a significant impact on the datavolume.
The data in the E fact table is compressed and occupies lesser space than F fact table. Archives October September August 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.
April 18, at The F-table uses b-tree indexes the E-Table uses bitmap indexes. In this case, the entries where all key figures are equal to 0 are deleted from the fact table. Subsequent compression of the same InfoCube will be from the beginning again.