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.

Author: Mazukasa Zushura
Country: Libya
Language: English (Spanish)
Genre: Relationship
Published (Last): 11 September 2008
Pages: 460
PDF File Size: 19.76 Mb
ePub File Size: 8.76 Mb
ISBN: 834-9-67782-392-9
Downloads: 98064
Price: Free* [*Free Regsitration Required]
Uploader: Goltigore

You must be absolutely certain that the data loaded into the InfoCube is correct. So in short Compression: Conclusion There are a couple of advantages and disadvantages compressing an InfoCube or not.

What happens to the data in a compression? Compressing the fact table is one option that optimized the access to basis infocubes. During compression, these records are summarized to one entry with the request ID ‘0’.

By choice the compression can be all or only part of the requests that have been loaded. Compression of Non cumulative InfoCubes are mandatory. With non-cumulative InfoCubes, the marker for non-cumulatives is also updated. You can schedule the function immediately or in the background.

WelcomeGuest Login Register. When you load data into the InfoCube, entire requests can be added at the same time. One advantage of the request ID concept is that you can subsequently delete complete requests from the InfoCube. You can execute the query once compression is finished. Therefore compression is done best during non-reporting hours or weekends.

You can schedule compression as part of a process chain. Compressing a fact table is done in the InfoCube administration and is based on the request id number. Every InfoCube has a datapackage dimension that holds the request id. An InfoCube is loaded request by request, i.


Features You can choose request IDs and release them to be compressed. 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.

When you load a data target, say a cube, the data is stored in the F fact table. During upload of data, a full request will always be inserted into the F-fact table. SAP Note Too many uncompressed request f table partitions.

Hi Martin, Nice document. The F-table uses b-tree indexes the E-Table uses bitmap indexes.


For that reason bw provides a couple features that help to increase performance. Improve performance further with partitioning the fact table.

The data in the E fact table is compressed and occupies lesser space than F fact table. You can eliminate these disadvantages by compressing data and bringing data from different requests together into one single request request ID 0. Yes, you can kill the compression.

For performance reasons, and to save space on the memory, compress a request as soon as you have established that it is correct and is not to be removed from the InfoCube. 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.

To find out more, including how to control cookies, see here: This makes it possible to pay particular attention to individual requests.

With non-cumulative InfoCubes, compression has an additional effect on query performance. This site uses cookies. That would be helpful for any learner. In this case, the entries where all key figures are equal to 0 are deleted from the fact table.


This allows bw to store the data in a compressioh which is not necessarily required from a business perspective. Collapse data by request id Compressing a fact table is done in the InfoCube administration and is based on the request id number.

Improve performance – by compressing the fact table #SAP #BW | SAP Blogs

Create a free website or blog at WordPress. Compressing one request takes approximately 2. This feature enables you, for example, to delete a request from the F-fact table after the upload.

Can cube compression be run in a way, that reporting stays available while it is executed?

SAP infocube compression tables

Archives October September August Comments Leave a Comment Categories Uncategorized. Open link in a new tab. 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. What is a compression exactly? For performance reasons, you should compress subsequent delta requests. October 11, at 6: If you are using an Oracle database as your database, you can also execute queries on the relevant InfoCube while compression is running.

You can choose request IDs and release them to be compressed. You must be Logged on to comment or reply to a post. Secondary Index usually abap tablesBitmap Index Bitmap indexes are created by default on each dimension column of a fact tableand B-Tree Index. Zero Elimination means deleting the record from the cube after compression if and only if, the entire key figures of the particular record is zero.