<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Running SQL Trace in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/running-sql-trace/m-p/3545999#M853124</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Well using SQL trace&lt;/P&gt;&lt;P&gt;like as follows: &lt;/P&gt;&lt;P&gt;Goto transaction ST05. Press TRACE ON.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Execute your transaction .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Come back to this screen and click TRACE OFF.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then check the trace details.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="-------------------------------------------------------------------------------" /&gt;&lt;P&gt;You end up getting unnecessary details &lt;/P&gt;&lt;P&gt;Lets say you have to analyze your particular SQL query, &lt;/P&gt;&lt;P&gt;1. put a breakpoint at the select statement and execute the transaction , as it stops at your breakpoint , run SQL trace in seperate session.&lt;/P&gt;&lt;P&gt;2. Trace ON&lt;/P&gt;&lt;P&gt;3. Execute the select statement.&lt;/P&gt;&lt;P&gt;4. Trace OFF&lt;/P&gt;&lt;P&gt;5. Analyze.&lt;/P&gt;&lt;P&gt;In this way you can analyze your particular select query &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SQL tracehttp://help.sap.com/saphelp_47x200/helpdata/en/d1/801f7c454211d189710000e8322d00/content.htm&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Kiran Sure&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 01 Apr 2008 13:09:13 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-04-01T13:09:13Z</dc:date>
    <item>
      <title>Running SQL Trace</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/running-sql-trace/m-p/3545998#M853123</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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? &lt;/P&gt;&lt;P&gt;Any pointers will be helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Keerthi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Apr 2008 13:05:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/running-sql-trace/m-p/3545998#M853123</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-01T13:05:51Z</dc:date>
    </item>
    <item>
      <title>Re: Running SQL Trace</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/running-sql-trace/m-p/3545999#M853124</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Well using SQL trace&lt;/P&gt;&lt;P&gt;like as follows: &lt;/P&gt;&lt;P&gt;Goto transaction ST05. Press TRACE ON.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Execute your transaction .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Come back to this screen and click TRACE OFF.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then check the trace details.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="-------------------------------------------------------------------------------" /&gt;&lt;P&gt;You end up getting unnecessary details &lt;/P&gt;&lt;P&gt;Lets say you have to analyze your particular SQL query, &lt;/P&gt;&lt;P&gt;1. put a breakpoint at the select statement and execute the transaction , as it stops at your breakpoint , run SQL trace in seperate session.&lt;/P&gt;&lt;P&gt;2. Trace ON&lt;/P&gt;&lt;P&gt;3. Execute the select statement.&lt;/P&gt;&lt;P&gt;4. Trace OFF&lt;/P&gt;&lt;P&gt;5. Analyze.&lt;/P&gt;&lt;P&gt;In this way you can analyze your particular select query &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SQL tracehttp://help.sap.com/saphelp_47x200/helpdata/en/d1/801f7c454211d189710000e8322d00/content.htm&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Kiran Sure&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Apr 2008 13:09:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/running-sql-trace/m-p/3545999#M853124</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-01T13:09:13Z</dc:date>
    </item>
    <item>
      <title>Re: Running SQL Trace</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/running-sql-trace/m-p/3546000#M853125</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Keerthi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Go through this link.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[http://saptechnical.com/Tutorials/ABAP/SQLTrace/page1.htm]&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You will be able to understand SQL trace clearly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Babul.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: babulreddy kurapatti on Apr 1, 2008 3:18 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Apr 2008 13:17:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/running-sql-trace/m-p/3546000#M853125</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-01T13:17:40Z</dc:date>
    </item>
    <item>
      <title>Re: Running SQL Trace</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/running-sql-trace/m-p/3546001#M853126</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;this blog is even better:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/people/siegfried.boes/blog/2007/09/05/the-sql-trace-st05-150-quick-and-easy&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rewards should go to the author.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Apr 2008 13:29:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/running-sql-trace/m-p/3546001#M853126</guid>
      <dc:creator>ThomasZloch</dc:creator>
      <dc:date>2008-04-01T13:29:11Z</dc:date>
    </item>
    <item>
      <title>Re: Running SQL Trace</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/running-sql-trace/m-p/3546002#M853127</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thomas, you are very kind &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Read the blog he mentioned, especially section is the most useful summary of the SQL trace.&lt;/P&gt;&lt;P&gt;That view gives you a very good overview and allows to solve 95% of the usual performance problems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Siegfried&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Apr 2008 15:18:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/running-sql-trace/m-p/3546002#M853127</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-01T15:18:03Z</dc:date>
    </item>
  </channel>
</rss>

