cancel
Showing results for 
Search instead for 
Did you mean: 

Runtime Issue

erdem_sephanelioglu
Participant
0 Kudos

Dear All,

My client's feedback regarding 20milion-data-containing PP cube, the runtime is quite a lot. What are the possible methods for letting the BEx query generate results relatively in shorter time?

Which out of all gives the most effective outcome?

Thank you.

Eddy.

Accepted Solutions (0)

Answers (3)

Answers (3)

sapna_jgurudutt
Active Contributor
0 Kudos

Hi Eddy,

Can you please refer the following notes and check whether it helps you:

1127156 - Safety belt: Result set is too large

1681396 - Query Performance

Thanks & Regards,

Sapna

Former Member
0 Kudos

Hi Eddy,

If number of records in milions, it requires periodic compression of cube data , it will reduce query  run time. Please revisit your query design , it will also help you to improve query performance,

http://myhelp.uky.edu/rwd/HTML/BW/BEX_Query_Guidelines.pdf

Hope this document will serve your query.

Otherwise broadcast query in cache.

Regards,

Anand Mehrotra.

arvind_doomra
Active Contributor
0 Kudos

Dear Eddy,

Please go through the below note as this tells you every aspects of Query performance.

SAP Note 1681396 : Query Performance

Regards,

Arvind

RamanKorrapati
Active Contributor
0 Kudos

Hi Eddy,

Please search the forum, you will get lots discussed threads.

Please look at the below points which are helpful.

1.Use very less characters in initial report, place remaining in free chars

2. Line item Dimension

3. Use aggregates or BWA indexes

4. Query read mode(RSRT)

5. OLAP Cache

6. Partition of info cube

7. Compression of info cube

8. DB Statistics

http://wiki.sdn.sap.com/wiki/display/BI/How+to+Improve+Query+Performance+-+A+Checklist

Thanks