abap runtime analysis

[Former Member]

need help

when we go for runtime analysis and when we gor for sql trace

pls explain with example

thanks in advance

[Former Member]

Hi,

Runtime analysis: se30 : to check our overall program efficiency or quality.

this analysis would be conculed by colours.

this is mainly checked to know our progam performance once got required o/p, then use this to know our program speed or performance.

Sqltrace : st05 : to check our sql statements.

this t/r have to run parallelly to our program.

if se30 shows the data base in red clor,then we have to check this sqltrace t/r to know which sql statement geeting bad performance.

[former_member156446]

http://www.sapbrainsonline.com/TOOLS/RUNTIMEanalysis/SAP_runtime_analysis.html

http://www.google.com/url?sa=t&ct=res&cd=1&url=https%3A%2F%2Fwww.sdn.sap.com%2Firj%2Fsdn%2Fgo%2Fport...

[Former Member]

Hi Vibhu,

Please Check this,

System Trace: Transaction ST01 lets you do various levels of system trace such as authorization checks, SQL traces, table/buffer trace etc. It is a general Basis tool but can be leveraged for BW.

Workload Analysis: You use transaction code ST03

Database Performance Analysis: Transaction ST04 gives you all that you need to know about whatu2019s happening at the database level.

Performance Analysis: Transaction ST05 enables you to do performance traces in different are as namely SQL trace, Enqueue trace, RFC trace and buffer trace.

ABAP Runtime Analysis Tool: Use transaction SE30 to do a runtime analysis of a transaction, program or function module. It is a very helpful tool if you know the program or routine that you suspect is causing a performance bottleneck.

Cheers

Mohinder Singh Chauhan

[Former Member]

Hi

Run time analysis transaction SE30 :This transaction gives all the analysis of an ABAP program with respect to the database and the non-database processing. 

SQL Trace transaction ST05: The trace list has many lines that are not related to the SELECT statement in the ABAP program. This is because the execution of any ABAP program requires additional administrative SQL calls. To restrict the list output, use the filter introducing the trace list.

The trace list contains different SQL statements simultaneously related to the one SELECT statement in the ABAP program. This is because the R/3 Database Interface - a sophisticated component of the R/3 Application Server - maps every Open SQL statement to one or a series of physical database calls and brings it to execution. This mapping, crucial to R/3s performance, depends on the particular call and database system. For example, the SELECT-ENDSELECT loop on a particular database table of the ABAP program would be mapped to a sequence PREPARE-OPEN-FETCH of physical calls in an Oracle environment.

The WHERE clause in the trace list's SQL statement is different from the WHERE clause in the ABAP statement. This is because in an R/3 system, a client is a self-contained unit with separate master records and its own set of table data (in commercial, organizational, and technical terms). With ABAP, every Open SQL statement automatically executes within the correct client environment. For this reason, a condition with the actual client code is added to every WHERE clause if a client field is a component of the searched table.

To see a statement's execution plan, just position the cursor on the PREPARE statement and choose Explain SQL. A detailed explanation of the execution plan depends on the database system in use.

[Former Member]

hi vibhu,

Runtime analysis shows you how long it takes to process ABAP code, from single statements to a complete transaction whereas The SQL Trace function is an on-demand log of selected SQL statements that are issued against the database through the Open SQL Engine.

Best of luck,

Bhumika

[Former Member]

Hi,

Runtime Analysis tool makes it possible to take detailed measurements of the runtime requirements of your programs. This lets you locate the source code blocks in your program that are responsible for poor performance and tune them accordingly.

The SQL TRACE allows you to precisely analyze and track the database accesses that the database interface in the SAP system initiates. This makes the trace an effective tool for performance analysis.

Regards

Abhijeet