Q

Slow BW reporting with 150m rows infocube

Slow query reports can be the result of an improper infocube. FInd out if your infocube is too big here.

I have a problem. While executing a query, BW is very slow and sometimes I get a time-out error. I have created the indexes, statistics and aggregates on the cube to improve the performance, but the report is very slow, and the cube has a huge volume of data of approximately 150m rows. I am retrieving the data from a third party so please let me know if there is any other way to improve the performance of the cube so that I can execute my report faster.
150m rows in an infocube is not considered that big in BW and should not cause any serious performance issues. Make sure the cube has been designed properly considering all the necessary performance aspects.
This was first published in September 2006
This Content Component encountered an error

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:

-ADS BY GOOGLE

SearchManufacturingERP

SearchOracle

SearchDataManagement

SearchAWS

SearchBusinessAnalytics

SearchCRM

SearchContentManagement

SearchFinancialApplications

Close