Query Performance

[Former Member]

Hi experts,

I am going through one SAP doc about query performance.

As I understood,we use ST03(WorkLoad Monitor) t-code> Expert Mode>Today-->Query..then we see various percentages

how do we notice here which is having bad performance from these statistics....and how do we go forward from here to improve that query performance?

whats the use of RSRT when we are already using ST03?I am a bit confused...

Thanks.

P Olin

[Former Member · Accepted solution]

Hello,

The main functionality of RSRT (Query monitor) to monitor the performance of a query. The users run the query and we collect the statistics in BW statistics. If the query runs slow or has some problems like authorization, not reading an aggregate, not using a info provider that is part of a multi provider, then, we simulate the query execution in various scenarios.

The Query Monitor (transaction RSRT) allows you to execute queries and to trace queries in a debug mode with several parameters (e.g., do not use aggregates, do not use buffer, show SQL statement).In the debug mode, you can investigate if the correct aggregate(s) are used and which statistics the query execution generates. For checking reasons, you can switch off the usage of aggregates, switch to no parallel processing (see for more details in the MultiProvider section) or display the SQL statement and the run schedule.

Moreover, you set some performance-related query features in RSRT: read mode and OLAP query

cache mode.

If you discover single queries that you wish to improve in terms of performance,you should execute them in RSRT in the debug mode, and analyze which aggregates are used and which statistics are generated.

You can find lots more in the PDF, link given below:

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/10fb4502-111c-2a10-3080-df0e41d44bb3&override...

Use ST03N ->

BW System load values to recognize the problem. Use the number given in table 'Reporting - InfoCubes:Share of total time (s)'

to check if one of the columns %OLAP, %DB, %Frontend shows a high number in all InfoCubes.

Regards,

[former_member209721]

I confirm with previous posts : RSRT and RSRT1 are good tools to execute in debug mode and set properties (such as Cache options) for BEX queries. It is also a good tool to analyse if a query was correctly defined in terms of performance (technical performance in RSRT1)

[former_member182516]

in addition to all the above post for more info please check the below link

SDNWeblogs_BusinessIntelligencebi%2528SAPNetworkWeblogs%253ABusinessIntelligence+%2528BI%2529%2529

REgards

KP

[Former Member]

In RSRT (BI7 RSRT2) you can do several things:

1- setup chache for each query

2- the behaviour of query: should it read all the data at once or free characteristics later when you navigate

3- Figure out which aggregates are needed

4- debug the query

As for ST03; I prefer to use BW statistics rather than ST03

Aban