Skip to Content
author's profile photo Former Member
Former Member

Decrease Olap time

Hi everybody,

How can i decrease the olap time (qolaptime in table rssdstat) when i execute query? without changing hardware?

any ideas?

Thank a lot.

DP

Add a comment
10|10000 characters needed characters exceeded

Related questions

5 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Sep 01, 2006 at 03:35 AM

    HI DP,

    Here are some things to keep in mind when u have problems with DB Runtime, Frontend runtime or OLAP runtime..

    A)High Database Runtime

    Check if an aggregate is suitable (use All data to get values "selected records to transferred records", a high number here would be an indicator for query performance improvement using an aggregate)

    Check if database statistics are update to data for the Cube/Aggregate, use TX RSRV output (use database check

    for statistics and indexes)

    Check if the read mode of the query is unfavourable - Recommended (H)

    B)High OLAP Runtime

    Check if a high number of Cells transferred to the OLAP (use "All data" to get value "No. of Cells")

    a) Use RSRT technical Information to check if any extra OLAP-processing is necessary (Stock Query, Exception Aggregation, Calc. before Aggregation, Virtual Char. Key Figures, Attributes in Calculated Key Figs, Time-dependent Currency Translation) together with a high number of records transferred.

    b) Check if a user exit Usage is involved in the OLAP runtime?

    c) Check if large hierarchies are used and the entry hierarchy level is as deep as possible. This limits the levels of the hierarchy that must be processed.

    Use SE16 on the inclusion tables and use the List of Value feature on the column successor and predecessor to see which entry level of the hierarchy is used.

    C)High Frontend Runtime

    1)Check if a very high number of cells and formattings are transferred to the Frontend ( use "All data" to get value "No. of Cells") which cause high network and frontend (processing) runtime.

    2) Check if frontend PC are within the recommendation (RAM, CPU Mhz)

    3) Check if the bandwidth for WAN connection is sufficient.

    hopr this helps,

    regards,

    kishore karnati

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      One more thing,

      High Frontend Runtime

      1)Check if a very high number of cells and formattings are transferred to the Frontend ( use "All data" to get value "No. of Cells") which cause high network and frontend (processing) runtime.

      how can i set this one too,

      Regards,

      Robyn.

  • author's profile photo Former Member
    Former Member
    Posted on Aug 31, 2006 at 03:07 PM

    Hi,

    Hope you have enabled OLAP caches in the first place.

    This is will be quick win.

    Regards

    Balaji

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 31, 2006 at 03:27 PM

    May be the following link help you

    http://help.sap.com/saphelp_nw04/helpdata/en/41/b987eb1443534ba78a793f4beed9d5/frameset.htm

    Regs

    Gopi

    Assign points if it is useful

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 31, 2006 at 09:52 PM

    Hi,

    Thanks for the responses.

    I have enough caches for query (olap cache), but I believed the OLAP cache improved the db time. it's truth?

    It's a same thing for aggregates, no?

    Ok for Query read modes (A/X/H), if I use the parameters X or A.

    Ok for precalculation, i'll try.

    I don't know what are 'Value Sets' and 'Static Web Pages'. but i'll search.

    thanks a lot.

    bye.

    DP

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      If the user's query can find the results in the OLAP cache, then the DB time is eliminated - BW does not need to run the SQL query at all.

      There are query settings and variable settings that impact the likelihood that teh results will be found in the OLAP cache. SDN has some docs on OLAP cache and there are threads in the BI forums that go into this more.

      Generally, the Query Read Mode option SAP recommends is the one that is based on navigation and hierarchy, which I guess is the X option. Changing to the Read All data can really lengthen the DB time, and probably only makes sense inlimited situations,e.g if you wanted to run a query with Reporting Agent to warmup the cache for subsquent query execution to use.

  • author's profile photo Former Member
    Former Member
    Posted on Sep 03, 2006 at 08:42 PM

    Thank you everyone.

    With the ST03, I'll calculate the improvement of the performance.

    DP

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.