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):||13 January 2012|
|PDF File Size:||17.86 Mb|
|ePub File Size:||17.59 Mb|
|Price:||Free* [*Free Regsitration Required]|
By choice the compression can be all or only part of the requests that have been loaded. Nice information for fresher…. To achieve this each InfoCube consist out of two two fact tables one with a request id and one without it. How it works During upload of data, a full request will always be inserted into the F-fact table.
An InfoCube is loaded request by request, i. Improve performance further with partitioning the fact table.
In this case, the entries where all key figures are equal to 0 co,pression deleted from the fact table. What is a compression exactly?
To find out more, including how to control cookies, see here: An aggregation of the data asp datapackages by removing the request id can shrink the datavolume of the factable dramatically without any downfall from a business perspective.
You must be absolutely certain that the data loaded into the InfoCube is correct. 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.
Each of these requests has its own request ID, which is included in the fact table in the package dimension. October 11, at 7: 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 lnfocube request ID.
SAP infocube compression tables
Compressing one request takes approximately 2. The data in the E fact table is compressed and occupies lesser space than F fact table. Create a free website or blog at WordPress. 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. One advantage of the request ID concept is that you can subsequently delete complete requests from the InfoCube. You must be Logged on to comment or reply to a post.
What happens to the data in a compression?
Compression – SAP NetWeaver Business Warehouse – SCN Wiki
You cannot run zero-elimination for InfoCubes that contain non-cumulative values. SAP Note Too many uncompressed request f table partitions. Yes, you can kill the compression. If you perform compression for a non-cumulative InfoCube, the compression time including imfocube time to update the markers is about 5 ms per data record. This unnecessarily increases the volume of data and affects system performance when you analyze data, since each time comptession execute a query, the system has to perform aggregation using the request ID.
Improve performance – by compressing the fact table #SAP #BW
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. Non cumulative Key Figures don’t maintain data in the InfoCube but the value is calculated at the run time of the query. Can I kill a compression? October 11, at 8: April 18, at Can cube compression be run in a way, that reporting stays available while it is executed? You can schedule the function immediately or in the background.