Q

Compression: useful for loading and reporting in BW?

Learn how compression plays a role between the E and F tables in BW cube loading and reporting. Jay Narayanan, BW and BI expert, explains how this works.

How is compression useful for loading and reporting? When should I compress, and how do I identify that the cube needs to be compressed? Does it have anything to do with the landscape?
Hi,

BW cubes have mainly two fact tables -- F and E tables. The data is always loaded to the F fact table and the compression

process moves the data from the F to the E fact table.

If your F fact table becomes too big, your load process will considerably slow down depending on the volume. Also if the cube is compressed the query performance will improve due to various reasons. It is best to compress the cube every day, keeping only three or four days of non-compressed data.

This was first published in October 2005

Dig deeper on Business intelligence software

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

SearchDataManagement

SearchAWS

SearchContentManagement

SearchCRM

SearchOracle

SearchSAP

SearchSQLServer

Close