<?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: Improving Select Query Performance in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/improving-select-query-performance/m-p/9408371#M1736569</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ashwin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By any chance, can you add those three missed primary key fields in the where clause?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Column3 - Primary Key&lt;/P&gt;&lt;P&gt;Column4 - Primary Key&lt;/P&gt;&lt;P&gt;Column5 - Primary Key&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Venkatesh.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 18 Apr 2013 13:04:08 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2013-04-18T13:04:08Z</dc:date>
    <item>
      <title>Improving Select Query Performance</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/improving-select-query-performance/m-p/9408369#M1736567</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Good Day! &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a custom table with following columns&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MANDT&amp;nbsp; - Primary Key&lt;/P&gt;&lt;P&gt;Column2 - Primary Key&lt;/P&gt;&lt;P&gt;Column3 - Primary Key&lt;/P&gt;&lt;P&gt;Column4 - Primary Key&lt;/P&gt;&lt;P&gt;Column5 - Primary Key&lt;/P&gt;&lt;P&gt;Column6 &lt;/P&gt;&lt;P&gt;Column7 &lt;/P&gt;&lt;P&gt;Column8 &lt;/P&gt;&lt;P&gt;Column9 &lt;/P&gt;&lt;P&gt;Column10 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a select query which takes long time to process.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If not&amp;nbsp; itab_select is initial&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Select Column2 &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Column3&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Column4&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Column5&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Column6&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Column7&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Column8&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Column9&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Column10&lt;/P&gt;&lt;P&gt;&amp;nbsp; into itab&lt;/P&gt;&lt;P&gt;for all entries in itab_select&lt;/P&gt;&lt;P&gt;where column2 = itab_select-col2&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; and&amp;nbsp; column3 = itab_select-col3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;endif.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This table has 12 million records. &lt;/P&gt;&lt;P&gt;250000 records keep getting insterted into this table via a Modify DTAB statement each day.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. To overcome the performance issue in the select query, Is it a good idea to create a secondary index on column2, column3 only. &lt;/P&gt;&lt;P&gt;Note I am not including MANDT in the secondary index.&lt;/P&gt;&lt;P&gt;2. Will there be performance issues in record insertion as the table is updated frequently (every 30 mins) and upto 250000 records are instered per day.&lt;/P&gt;&lt;P&gt;3. Is there any other recommendation to improve query performance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Ashwin Bhat&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Apr 2013 07:46:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/improving-select-query-performance/m-p/9408369#M1736567</guid>
      <dc:creator>ashwin_bhat</dc:creator>
      <dc:date>2013-04-16T07:46:29Z</dc:date>
    </item>
    <item>
      <title>Re: Improving Select Query Performance</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/improving-select-query-performance/m-p/9408370#M1736568</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;If Select query is the issue of performance then i suggest to follow below strategy;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Use PACKAGE SIZE in select query i.e fetching of data in set of packages .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. Use of OPEN &amp;amp; FETCH CURSOR techniques for data selection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. Even if above method doesn't lead to improvement then create Secondary index for the table..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Nandi.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Apr 2013 11:50:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/improving-select-query-performance/m-p/9408370#M1736568</guid>
      <dc:creator>former_member197425</dc:creator>
      <dc:date>2013-04-16T11:50:57Z</dc:date>
    </item>
    <item>
      <title>Re: Improving Select Query Performance</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/improving-select-query-performance/m-p/9408371#M1736569</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ashwin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By any chance, can you add those three missed primary key fields in the where clause?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Column3 - Primary Key&lt;/P&gt;&lt;P&gt;Column4 - Primary Key&lt;/P&gt;&lt;P&gt;Column5 - Primary Key&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Venkatesh.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Apr 2013 13:04:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/improving-select-query-performance/m-p/9408371#M1736569</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-04-18T13:04:08Z</dc:date>
    </item>
    <item>
      <title>Re: Improving Select Query Performance</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/improving-select-query-performance/m-p/9408372#M1736570</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1. Create a secondary index with Col2 and Col3.&lt;/P&gt;&lt;P&gt;2. Sort itab_select by col2 col3.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Delete adjacent duplicate rows from itab_select compairing col2 col3. -- Before select .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If this doesn't help then try the package size in select.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This might help u..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reards&lt;/P&gt;&lt;P&gt;Sudip. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Apr 2013 14:03:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/improving-select-query-performance/m-p/9408372#M1736570</guid>
      <dc:creator>sudipDas</dc:creator>
      <dc:date>2013-04-18T14:03:55Z</dc:date>
    </item>
  </channel>
</rss>

