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: Dor Nikotaxe
Country: Bulgaria
Language: English (Spanish)
Genre: Art
Published (Last): 1 September 2018
Pages: 348
PDF File Size: 4.81 Mb
ePub File Size: 12.44 Mb
ISBN: 301-7-55153-941-3
Downloads: 3258
Price: Free* [*Free Regsitration Required]
Uploader: Magami

Compressing a fact table is done in the InfoCube administration and is based on the request id number.

Can I kill a compression? When you load data into the InfoCube, entire requests can be added at the same time. Compressed E-Fact table — Compression cannot be undone and individual requests cannot be differentiated anymore. Any request mid-compression will be rolled back. Compressing the fact table is one option that optimized the access to basis infocubes.

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.

What happens to the data in a compression? Index, Primary Index The primary index is created automatically when the table is created in the database.

How it works During upload of data, a full request will always be inserted into the F-fact table. You cannot run zero-elimination for InfoCubes that contain non-cumulative values. A compresslon tachments 0 Page History. So in short Compression: Compressing one request takes approximately 2.

By choice the compression can be all or only part of the comlression that have been loaded. Therefore compression is done best during non-reporting hours or weekends.


The F-table uses b-tree indexes the E-Table uses bitmap indexes. If you perform compression for a non-cumulative InfoCube, the compression time including the time to update the markers is about 5 ms per data record. For performance reasons, you should compress subsequent delta requests.

Infocube Compression | SAP BW Overview

To find out more, including how to control cookies, see here: 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 Compfession.

To achieve this each InfoCube consist out of two two fact tables one with a request id and comrpession without it. 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.

What happens when we compress InfoCube? Nice information for fresher….

Every InfoCube has a datapackage dimension that holds the request id. If the cube is compressed, the data in the F fact table is transferred to the E fact table. When you load a data target, say a cube, the data is stored in the F fact table.


You can choose request IDs and release them to be compressed. An InfoCube is loaded request by request, i. Purpose To explain the concept and reasons behind compressing requests in InfoCubes Overview InfoCubes should be compressed regularly. 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. October 10, 2 minute read.

Yes, you can kill the compression.

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

However, the request ID concept can also cause the same data record where all characteristics are the same except the request ID to appear more than once in the fact table. That would be helpful for any learner. Comments Leave a Comment Categories Uncategorized.

  LENZE 8100 PDF

If you are using an Oracle database as your database, you can also execute queries on bo relevant InfoCube while compression is running. You can schedule the function immediately or in the background.

During upload of data, a full request will always be inserted into the F-fact table. One advantage of the request ID concept is that you can cpmpression delete complete requests from the InfoCube. For that reason bw provides a couple features that help to increase performance. Open link in a new tab. WelcomeGuest Login Register. Secondary Index usually abap tablesBitmap Index Bitmap indexes are created by default on each dimension column of a fact tableand B-Tree Index.

By continuing to use this website, you agree to their use. Search or use up and down arrow keys to select an item. This site uses cookies. Compresskon 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 infocueb. Compression of Non cumulative InfoCubes are mandatory.

This function is critical, since you cannot delete compressed data from the InfoCube using its request ID.