<?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: SQL Performance Tuning Worklist SWLT help in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/sql-performance-tuning-worklist-swlt-help/m-p/9599515#M1758382</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here is the documentation&lt;/P&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;H2&gt;&lt;SPAN class="pasted-list-info"&gt;1.1&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;SQL Performance Tuning&lt;BR /&gt;Worklist&lt;/H2&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;H3&gt;&lt;SPAN class="pasted-list-info"&gt;1.1.1&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;Purpose&lt;/H3&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV style="text-indent: 0in;"&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;The &lt;STRONG&gt;SQL Performance Tuning Worklist &lt;/STRONG&gt;tool (transaction &lt;STRONG&gt;/SWLT&lt;/STRONG&gt;)&lt;BR /&gt;enables you to find ABAP SQL code that has potential for performance&lt;BR /&gt;improvement in productive business processes. This tool combines new ABAP code&lt;BR /&gt;scans (ABAP Test Cockpit or Code Inspector &lt;STRONG&gt;/SCI&lt;/STRONG&gt;) with monitoring and&lt;BR /&gt;analysis utilities (SQL Monitor and Coverage Analyzer), and automatically&lt;BR /&gt;creates a condensed worklist. The resulting findings allow you to rank the&lt;BR /&gt;worklist according to specific performance issues and your business relevance.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV style="text-indent: 0in;"&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;Prior to analyzing static checks, appropriate ABAP test cockpit&lt;BR /&gt;runs must be performed in the case of systems SAP EhP2 and upwards for SAP&lt;BR /&gt;NetWeaver 7.0 SP 12, and their results must be replicated into the relevant&lt;BR /&gt;system. In the case of older systems (&amp;lt; SAP EhP2 for SAP NetWeaver 7.0, SP&lt;BR /&gt;12), static checks must be performed with the Code Inspector instead.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;H5&gt;&lt;STRONG style=": ; color: windowtext; Times New Roman&amp;amp;quot: ; sans-serif&amp;amp;quot: ; font-family: &amp;amp;quot; Arial&amp;amp;quot: ; mso-fareast-font-family: &amp;amp;quot; ,&amp;amp;quot: ;"&gt;Recommendation&lt;/STRONG&gt;&lt;/H5&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV style="text-indent: 0in;"&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;For the execution of static checks (ABAP Test Cockpit or Code&lt;BR /&gt;Inspector) we recommend using the pre-defined Code Inspector variant &lt;/SPAN&gt;&lt;TT&gt;&lt;SPAN style="color: black;"&gt;PERFORMANCE_DB&lt;/SPAN&gt;&lt;/TT&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV style="text-indent: 0in;"&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;Moreover, in case you are only interested in static check results&lt;BR /&gt;for SQL statements that have been recorded by the SQL Monitor, we advise you to&lt;BR /&gt;use the Code Inspector object collector &lt;/SPAN&gt;&lt;TT&gt;&lt;SPAN style="color: black;"&gt;CL_CI_COLLECTOR_SQLM_SNAPSHOT&lt;/SPAN&gt;&lt;/TT&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;("Objects of&lt;BR /&gt;SQLM-Snapshot"). This object collector allows restricting the inspection's&lt;BR /&gt;object set to objects that are contained in a previously recorded SQL Monitor &lt;STRONG&gt;/SQLMsnapshot which helps to optimize the performance and memory consumption of&lt;BR /&gt;the used scan and analysis tools.&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;H3&gt;&lt;SPAN class="pasted-list-info"&gt;1.1.2&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;Features&lt;/H3&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;Options for Object Selection&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV style="text-indent: 0in;"&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;You can select development objects that are suitable for analysis&lt;BR /&gt;using various criteria. For example, you can limit the objects to a particular&lt;BR /&gt;set of packages or a particular object type.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;Options for SQL Monitoring&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV style="text-indent: 0in;"&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;You can either use snapshots that already exist in the system for&lt;BR /&gt;SQL monitoring data or, if required, generate new ones.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;Managing Snapshots of SQL Monitor Data&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV style="text-indent: 0in;"&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;The snapshot management can be initiated either from the selection&lt;BR /&gt;screen of transaction SWLT (via the button "Manage Snapshots") or by&lt;BR /&gt;executing the report &lt;/SPAN&gt;&lt;TT&gt;&lt;SPAN style="color: black;"&gt;SWLT_SQLM_CREATE_SNAPSHOT&lt;/SPAN&gt;&lt;/TT&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;. You can generate new snapshots directly&lt;BR /&gt;from the local system or by specifying an RFC destination. Alternatively, you&lt;BR /&gt;can also upload a snapshot file previously created with the report &lt;/SPAN&gt;&lt;TT&gt;&lt;SPAN style="color: black;"&gt;RSQLM_DOWNLOAD_DATA&lt;/SPAN&gt;&lt;/TT&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;. In addition, there is an option to delete snapshots based on&lt;BR /&gt;their creation date.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;Options for Results Display from Static Checks&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;You can make adjustments for the&lt;BR /&gt;selection and display of results of static checks (ATC or Code Inspector).&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;Compressed Overview Display&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV style="text-indent: 0in;"&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;In accordance with your selection options, you will get a list of&lt;BR /&gt;results (findings) that, in the standard version, are sorted according to the&lt;BR /&gt;number of executions or the execution time. From here you already have the&lt;BR /&gt;possibility to detect the performance hotspots. From the overview display, you&lt;BR /&gt;can double-click the line in question and request the details view for runtime&lt;BR /&gt;data and data from the respective static check.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;Detailed View with SQL Monitoring Data&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV style="text-indent: 0in;"&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;Using the SQL Monitor Results display function, you can perform a&lt;BR /&gt;more advanced breakdown or analysis of the runtime data; in particular, you can&lt;BR /&gt;determine the entry point of the processes or DB operations.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;Detailed View with Results from Static Checks&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV style="text-indent: 0in;"&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;Using another detailed view, you can analyze the findings from the&lt;BR /&gt;static check with regard to their relevance for possible code optimization.&lt;BR /&gt;Here, the statements on priority, severity, and estimated work effort are of&lt;BR /&gt;particular relevance.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;Integration of Code Coverage&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;If no SQL data is available in the&lt;BR /&gt;system, you can evaluate the data from the code coverage.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;H3&gt;&lt;SPAN class="pasted-list-info"&gt;1.1.3&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;Activities&lt;/H3&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;The typical procedure for working&lt;BR /&gt;with SWLT transaction involves the following steps:&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;OL style="list-style-type: decimal;"&gt;&lt;LI&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;1. Launch transaction &lt;STRONG&gt;SWLT&lt;/STRONG&gt;.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;2. On the Selection Screen, specify the options for the object&lt;BR /&gt;selection, the SQL monitoring data, and for displaying the static check&lt;BR /&gt;findings.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;3. Choose &lt;STRONG&gt;Execute&lt;/STRONG&gt; (F8).&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;4. On the &lt;STRONG&gt;Aggregated Results Overview&lt;/STRONG&gt; screen, identify and&lt;BR /&gt;analyze the performance hotspots.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;5. On the &lt;STRONG&gt;Aggregated Results Overview &lt;/STRONG&gt;screen, double-click&lt;BR /&gt;the corresponding table row to open the detailed view.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;6. Analyze the details for the runtime data and the static check&lt;BR /&gt;findings.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 11 Sep 2013 19:39:08 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2013-09-11T19:39:08Z</dc:date>
    <item>
      <title>SQL Performance Tuning Worklist SWLT help</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sql-performance-tuning-worklist-swlt-help/m-p/9599509#M1758376</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Hi,&lt;/P&gt;&lt;P&gt;Does any one has experience running the tool SWLT. I do no find any documentation related to the tool.&lt;/P&gt;&lt;P&gt;Can someone through an insight.&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ashish Singh &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Aug 2013 03:43:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sql-performance-tuning-worklist-swlt-help/m-p/9599509#M1758376</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-08-08T03:43:00Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Performance Tuning Worklist SWLT help</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sql-performance-tuning-worklist-swlt-help/m-p/9599510#M1758377</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;you will find some documentation here soon .... .&lt;/P&gt;&lt;P&gt;We are reviewing it at the moment, so it should be available soon here.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hermann&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Aug 2013 07:59:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sql-performance-tuning-worklist-swlt-help/m-p/9599510#M1758377</guid>
      <dc:creator>HermannGahm</dc:creator>
      <dc:date>2013-08-08T07:59:35Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Performance Tuning Worklist SWLT help</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sql-performance-tuning-worklist-swlt-help/m-p/9599511#M1758378</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Aug 2013 16:02:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sql-performance-tuning-worklist-swlt-help/m-p/9599511#M1758378</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-08-08T16:02:52Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Performance Tuning Worklist SWLT help</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sql-performance-tuning-worklist-swlt-help/m-p/9599512#M1758379</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;Do we have any documentation made available for this tool ? Still not able to find in something in SCN for this tool.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Suma&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Aug 2013 09:40:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sql-performance-tuning-worklist-swlt-help/m-p/9599512#M1758379</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-08-28T09:40:38Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Performance Tuning Worklist SWLT help</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sql-performance-tuning-worklist-swlt-help/m-p/9599513#M1758380</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;not yet. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Coming soon.... in September...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(review is still in progress)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hermann&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Aug 2013 11:06:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sql-performance-tuning-worklist-swlt-help/m-p/9599513#M1758380</guid>
      <dc:creator>HermannGahm</dc:creator>
      <dc:date>2013-08-28T11:06:23Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Performance Tuning Worklist SWLT help</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sql-performance-tuning-worklist-swlt-help/m-p/9599514#M1758381</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi ashish , kindly share some screenshots and some other aspects of SWLT,&lt;/P&gt;&lt;P&gt;&lt;STRONG style="margin: -9px 0 0; font-size: 11px; background-color: #ffffff; color: #333333; text-align: right;"&gt;&lt;A _jive_internal="true" class="jiveTT-hover-user jive-username-link" href="https://answers.sap.com/people/ashish.singh19" id="jive-6861771347944105814987" style="padding: 0 3px 0 0; font-weight: normal; font-style: inherit; font-size: 20px; font-family: inherit; text-decoration: underline !important; color: #3778c7;"&gt;Ashish Singh&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Aug 2013 02:21:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sql-performance-tuning-worklist-swlt-help/m-p/9599514#M1758381</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-08-29T02:21:42Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Performance Tuning Worklist SWLT help</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sql-performance-tuning-worklist-swlt-help/m-p/9599515#M1758382</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here is the documentation&lt;/P&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;H2&gt;&lt;SPAN class="pasted-list-info"&gt;1.1&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;SQL Performance Tuning&lt;BR /&gt;Worklist&lt;/H2&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;H3&gt;&lt;SPAN class="pasted-list-info"&gt;1.1.1&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;Purpose&lt;/H3&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV style="text-indent: 0in;"&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;The &lt;STRONG&gt;SQL Performance Tuning Worklist &lt;/STRONG&gt;tool (transaction &lt;STRONG&gt;/SWLT&lt;/STRONG&gt;)&lt;BR /&gt;enables you to find ABAP SQL code that has potential for performance&lt;BR /&gt;improvement in productive business processes. This tool combines new ABAP code&lt;BR /&gt;scans (ABAP Test Cockpit or Code Inspector &lt;STRONG&gt;/SCI&lt;/STRONG&gt;) with monitoring and&lt;BR /&gt;analysis utilities (SQL Monitor and Coverage Analyzer), and automatically&lt;BR /&gt;creates a condensed worklist. The resulting findings allow you to rank the&lt;BR /&gt;worklist according to specific performance issues and your business relevance.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV style="text-indent: 0in;"&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;Prior to analyzing static checks, appropriate ABAP test cockpit&lt;BR /&gt;runs must be performed in the case of systems SAP EhP2 and upwards for SAP&lt;BR /&gt;NetWeaver 7.0 SP 12, and their results must be replicated into the relevant&lt;BR /&gt;system. In the case of older systems (&amp;lt; SAP EhP2 for SAP NetWeaver 7.0, SP&lt;BR /&gt;12), static checks must be performed with the Code Inspector instead.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;H5&gt;&lt;STRONG style=": ; color: windowtext; Times New Roman&amp;amp;quot: ; sans-serif&amp;amp;quot: ; font-family: &amp;amp;quot; Arial&amp;amp;quot: ; mso-fareast-font-family: &amp;amp;quot; ,&amp;amp;quot: ;"&gt;Recommendation&lt;/STRONG&gt;&lt;/H5&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV style="text-indent: 0in;"&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;For the execution of static checks (ABAP Test Cockpit or Code&lt;BR /&gt;Inspector) we recommend using the pre-defined Code Inspector variant &lt;/SPAN&gt;&lt;TT&gt;&lt;SPAN style="color: black;"&gt;PERFORMANCE_DB&lt;/SPAN&gt;&lt;/TT&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV style="text-indent: 0in;"&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;Moreover, in case you are only interested in static check results&lt;BR /&gt;for SQL statements that have been recorded by the SQL Monitor, we advise you to&lt;BR /&gt;use the Code Inspector object collector &lt;/SPAN&gt;&lt;TT&gt;&lt;SPAN style="color: black;"&gt;CL_CI_COLLECTOR_SQLM_SNAPSHOT&lt;/SPAN&gt;&lt;/TT&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;("Objects of&lt;BR /&gt;SQLM-Snapshot"). This object collector allows restricting the inspection's&lt;BR /&gt;object set to objects that are contained in a previously recorded SQL Monitor &lt;STRONG&gt;/SQLMsnapshot which helps to optimize the performance and memory consumption of&lt;BR /&gt;the used scan and analysis tools.&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;H3&gt;&lt;SPAN class="pasted-list-info"&gt;1.1.2&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;Features&lt;/H3&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;Options for Object Selection&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV style="text-indent: 0in;"&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;You can select development objects that are suitable for analysis&lt;BR /&gt;using various criteria. For example, you can limit the objects to a particular&lt;BR /&gt;set of packages or a particular object type.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;Options for SQL Monitoring&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV style="text-indent: 0in;"&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;You can either use snapshots that already exist in the system for&lt;BR /&gt;SQL monitoring data or, if required, generate new ones.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;Managing Snapshots of SQL Monitor Data&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV style="text-indent: 0in;"&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;The snapshot management can be initiated either from the selection&lt;BR /&gt;screen of transaction SWLT (via the button "Manage Snapshots") or by&lt;BR /&gt;executing the report &lt;/SPAN&gt;&lt;TT&gt;&lt;SPAN style="color: black;"&gt;SWLT_SQLM_CREATE_SNAPSHOT&lt;/SPAN&gt;&lt;/TT&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;. You can generate new snapshots directly&lt;BR /&gt;from the local system or by specifying an RFC destination. Alternatively, you&lt;BR /&gt;can also upload a snapshot file previously created with the report &lt;/SPAN&gt;&lt;TT&gt;&lt;SPAN style="color: black;"&gt;RSQLM_DOWNLOAD_DATA&lt;/SPAN&gt;&lt;/TT&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;. In addition, there is an option to delete snapshots based on&lt;BR /&gt;their creation date.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;Options for Results Display from Static Checks&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;You can make adjustments for the&lt;BR /&gt;selection and display of results of static checks (ATC or Code Inspector).&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;Compressed Overview Display&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV style="text-indent: 0in;"&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;In accordance with your selection options, you will get a list of&lt;BR /&gt;results (findings) that, in the standard version, are sorted according to the&lt;BR /&gt;number of executions or the execution time. From here you already have the&lt;BR /&gt;possibility to detect the performance hotspots. From the overview display, you&lt;BR /&gt;can double-click the line in question and request the details view for runtime&lt;BR /&gt;data and data from the respective static check.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;Detailed View with SQL Monitoring Data&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV style="text-indent: 0in;"&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;Using the SQL Monitor Results display function, you can perform a&lt;BR /&gt;more advanced breakdown or analysis of the runtime data; in particular, you can&lt;BR /&gt;determine the entry point of the processes or DB operations.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;Detailed View with Results from Static Checks&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV style="text-indent: 0in;"&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;Using another detailed view, you can analyze the findings from the&lt;BR /&gt;static check with regard to their relevance for possible code optimization.&lt;BR /&gt;Here, the statements on priority, severity, and estimated work effort are of&lt;BR /&gt;particular relevance.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;Integration of Code Coverage&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;If no SQL data is available in the&lt;BR /&gt;system, you can evaluate the data from the code coverage.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;H3&gt;&lt;SPAN class="pasted-list-info"&gt;1.1.3&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;Activities&lt;/H3&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;The typical procedure for working&lt;BR /&gt;with SWLT transaction involves the following steps:&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;OL style="list-style-type: decimal;"&gt;&lt;LI&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;1. Launch transaction &lt;STRONG&gt;SWLT&lt;/STRONG&gt;.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;2. On the Selection Screen, specify the options for the object&lt;BR /&gt;selection, the SQL monitoring data, and for displaying the static check&lt;BR /&gt;findings.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;3. Choose &lt;STRONG&gt;Execute&lt;/STRONG&gt; (F8).&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;4. On the &lt;STRONG&gt;Aggregated Results Overview&lt;/STRONG&gt; screen, identify and&lt;BR /&gt;analyze the performance hotspots.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;5. On the &lt;STRONG&gt;Aggregated Results Overview &lt;/STRONG&gt;screen, double-click&lt;BR /&gt;the corresponding table row to open the detailed view.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="color: black; font-size: 9.5pt;"&gt;6. Analyze the details for the runtime data and the static check&lt;BR /&gt;findings.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Sep 2013 19:39:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sql-performance-tuning-worklist-swlt-help/m-p/9599515#M1758382</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-09-11T19:39:08Z</dc:date>
    </item>
  </channel>
</rss>

