diffrence between st05 and se30

[Former Member]

hi experts please guide me wht st05 and se30 where we use and perpose.

[ferry_lianto]

Hi,

ST05 and SE30 are used for analysis of the performance of the program.

ST05

It is used for the detail analysis of the performance of the program, such as how the select statements are behaving, have we written the selects with all index keys etc. And also this is used to find user exits, BADIs etc.

SE30

It is the summary of the performance of the program. It tells you the time taken to execute your program by each server. For optimal performance program all the servers summary should be in green color... but we can judge the performance accurately by this.

Regards,

Ferry Lianto

[Former Member]

St05 is for sql trace

we can find out what r the indexes used and the tables used and time taken for databaASE FETCH

se30 is for run time analysis

[Former Member]

Hi

you can go through this link you came to know about ST05

http://help.sap.com/saphelp_nw04/helpdata/en/5a/ace273ca0211d194b500a0c94260a5/content.htm

regards

sha

[former_member194613]

Read the following blogs, then you should know the difference:

/people/siegfried.boes/blog/2007/11/13/the-abap-runtime-trace-se30--quick-and-easy

The ABAP Runtime Trace (SE30) - Quick and Easy

Besides the SQL Trace, the ABAP Runtime Analysis or ABAP Trace (transaction SE30) is the most important tool to use, if you want to test the performance of your program. Unfortunately, it can be seen in the forum and other sources that many people have questions about ABAP Trace. This blog will provide you with a quick introduction to ABAP Trace, show you how simple it is to execute, and tell you all you need to know for a basic performance analysis. Nov. 13, 2007

/people/siegfried.boes/blog/2007/09/05/the-sql-trace-st05-150-quick-and-easy

The SQL Trace (ST05) u2013 Quick and Easy

The SQL Trace, which is part of the Performance Trace (transaction ST05), is the most important tool to test the performance of the database. Unfortunately, information on how to use the SQL Trace and especially how to interpret its results is not part of the standard ABAP courses. This weblog tries to give you a quick introduction to the SQL Trace. It shows you how to execute a trace, which is very straightforward. And it tells how you can get a very condensed overview of the resultsthe SQL statements summarya feature that many are not so familiar with. The usefulness of this list becomes obvious when the results are interpreted. A short discussion of the u2018database explainu2019 concludes this introduction to the SQL Trace. Sep. 5, 2007

[Former Member]

Hi,

Regarding

ST05(SQL trace) provides one, the ability to analyze database select statements, the index being hit by out query,so on. Simply execute ST05 to turn on SQL trace, then execute the statement/program you want to analyze. Now turn off SQL trace using ST05 and click on list trace to view the details. You can also perform traces on other items such as authorization objects.

SE30(ABAP Runtime Analysis) - Returns the time take by a function/program/transaction w.r.t. three parameters - ABAP statements, database access and system access in microseconds and percentage. In addition it displays a detailed list giving the name of program and the statement called in a sequence in which they were called.

The advantage of SE30 over ST05 is that one can check the performance of the required program/function/tcode which in case of ST05, if one executes multiple transactions together then the ST05 output includes results of all those transactions, the complication increases if multiple users are logged on using the same SAP id.

You can use SAT in place of SE30 as the Transaction SE30 is currently being phased-out.

you can check below link:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20c64261-b3f8-2d10-06b4-fa41b2b93...

Regards,

Gopal

Edited by: Gopal23 on Mar 8, 2011 7:38 AM

[Former Member]

Hi,

ST05(SQL trace) is analyze database for select statements, index which is use in query and so on. Execute ST05 to turn on SQL trace, then execute the statement/program you want to analyze. then turn off SQL trace using ST05 and click on list trace to view the details. You can also perform traces on other items such as authorization objects etc.

SE30(ABAP Runtime Analysis) - which is returns the time take by a function/program/transaction w.r.t. three parameters - ABAP statements, database access and system access in microseconds and percentage. Also it displays a detailed list giving the name of program and the statement.

Regards,

Kunjan

[Former Member]

SE30 - Runtime Analysis Tool

This runtime analysis tools allows the ABAP/4 programmer to trace the tables used by the SAP dialog/reports programs. In the Analyze button

Displays the execution time of each statement in the program.

Tables

Displays the tables accessed during run time.

Group hit list

Displays the execution time of all the statements and grouping them based on the type of command. e.g. performs, SQL and internal tables used.

Hirarchy

Displays the execution time of each statement in the actual order in which were executed. Uses indentation to indicate the level of nesting of statements within subroutines.

Any tables use by the transaction or program can be easily trace with the runtime analysis tools.

ST05 -Performance Trace.

The Performance Trace allows you to record database access, locking activities, and remote calls of reports and transactions in a trace file and to display the performance log as a list. It also provides extensive support for analyzing individual trace records. The Performance Trace additionally offers wide support when analyzing individual trace records in detail.