‎2008 Apr 01 2:05 PM
Hi All,
Can anyone please tell me how i can run an SQL Trace on a program and drill-down to the performance of a particular query in the program?
Any pointers will be helpful.
Thanks in advance.
Regards,
Keerthi
‎2008 Apr 01 2:09 PM
Hi,
Well using SQL trace
like as follows:
Goto transaction ST05. Press TRACE ON.
Execute your transaction .
Come back to this screen and click TRACE OFF.
Then check the trace details.
-
You end up getting unnecessary details
Lets say you have to analyze your particular SQL query,
1. put a breakpoint at the select statement and execute the transaction , as it stops at your breakpoint , run SQL trace in seperate session.
2. Trace ON
3. Execute the select statement.
4. Trace OFF
5. Analyze.
In this way you can analyze your particular select query
SQL tracehttp://help.sap.com/saphelp_47x200/helpdata/en/d1/801f7c454211d189710000e8322d00/content.htm
Regards
Kiran Sure
‎2008 Apr 01 2:09 PM
Hi,
Well using SQL trace
like as follows:
Goto transaction ST05. Press TRACE ON.
Execute your transaction .
Come back to this screen and click TRACE OFF.
Then check the trace details.
-
You end up getting unnecessary details
Lets say you have to analyze your particular SQL query,
1. put a breakpoint at the select statement and execute the transaction , as it stops at your breakpoint , run SQL trace in seperate session.
2. Trace ON
3. Execute the select statement.
4. Trace OFF
5. Analyze.
In this way you can analyze your particular select query
SQL tracehttp://help.sap.com/saphelp_47x200/helpdata/en/d1/801f7c454211d189710000e8322d00/content.htm
Regards
Kiran Sure
‎2008 Apr 01 2:17 PM
Hi Keerthi,
Go through this link.
[http://saptechnical.com/Tutorials/ABAP/SQLTrace/page1.htm]
You will be able to understand SQL trace clearly.
Regards,
Babul.
Edited by: babulreddy kurapatti on Apr 1, 2008 3:18 PM
‎2008 Apr 01 2:29 PM
this blog is even better:
/people/siegfried.boes/blog/2007/09/05/the-sql-trace-st05-150-quick-and-easy
rewards should go to the author.
‎2008 Apr 01 4:18 PM
Thomas, you are very kind
Read the blog he mentioned, especially section is the most useful summary of the SQL trace.
That view gives you a very good overview and allows to solve 95% of the usual performance problems.
Siegfried