<?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: Performance tuning for UPDATE statement. in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-tuning-for-update-statement/m-p/5093677#M1182329</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;If you are updating from wark_area ( i.e Update  ...  from wa ) then it is allways better specify &lt;STRONG&gt;all key fields value&lt;/STRONG&gt; in the wark_area.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are updating from internal table ( Update ...  Table itab  ) then it is allways better specify all records of the table in sorted manner.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If in your Update statement having where clause then Try to specify all the &lt;STRONG&gt;key fields left-justifiedly with out any gaps&lt;/STRONG&gt; and if it is not possible then provide fields in where clause with-out missing any field .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are often using one or more than one &lt;STRONG&gt;same fields&lt;/STRONG&gt; ( other than key fields ) , you can create a &lt;STRONG&gt;secondary index with those fields.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Pinaki&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Pinaki Mukherjee on Feb 10, 2009 5:56 AM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 10 Feb 2009 04:55:43 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-02-10T04:55:43Z</dc:date>
    <item>
      <title>Performance tuning for UPDATE statement.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-tuning-for-update-statement/m-p/5093674#M1182326</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is an UPDATE statement that is very high in cost. I wanted to know whether there is any possibility of tuning the statement..by using any general methods like where statements,Indexes etc..?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Feb 2009 10:58:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-tuning-for-update-statement/m-p/5093674#M1182326</guid>
      <dc:creator>ameya_kulkarni3</dc:creator>
      <dc:date>2009-02-09T10:58:16Z</dc:date>
    </item>
    <item>
      <title>Re: Performance tuning for UPDATE statement.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-tuning-for-update-statement/m-p/5093675#M1182327</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;there are different UPDATE statements!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
 UPDATE   .... FROM WA
 UPDATE  .... FROM itab
 UPDATE  ... WHERE ...
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The last one has the same problems as any SELECT, either is a suitable index or not.&lt;/P&gt;&lt;P&gt;The first two should use the primary key, however, the arrayupdate FROM itab is of course better.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Siegfried&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Feb 2009 11:34:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-tuning-for-update-statement/m-p/5093675#M1182327</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-02-09T11:34:08Z</dc:date>
    </item>
    <item>
      <title>Re: Performance tuning for UPDATE statement.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-tuning-for-update-statement/m-p/5093676#M1182328</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;User array operation to UPDATE.&lt;/P&gt;&lt;P&gt;Move all the data the needs to be update to One internal Table.&lt;/P&gt;&lt;P&gt;After that user :&lt;/P&gt;&lt;P&gt;Update from Itab.&lt;/P&gt;&lt;P&gt;Beacuse there will be only One data base hit instead of many.&lt;/P&gt;&lt;P&gt;That will decrease load on DB Server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this will resolve the issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Gurpreet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Feb 2009 12:31:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-tuning-for-update-statement/m-p/5093676#M1182328</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-02-09T12:31:32Z</dc:date>
    </item>
    <item>
      <title>Re: Performance tuning for UPDATE statement.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-tuning-for-update-statement/m-p/5093677#M1182329</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;If you are updating from wark_area ( i.e Update  ...  from wa ) then it is allways better specify &lt;STRONG&gt;all key fields value&lt;/STRONG&gt; in the wark_area.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are updating from internal table ( Update ...  Table itab  ) then it is allways better specify all records of the table in sorted manner.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If in your Update statement having where clause then Try to specify all the &lt;STRONG&gt;key fields left-justifiedly with out any gaps&lt;/STRONG&gt; and if it is not possible then provide fields in where clause with-out missing any field .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are often using one or more than one &lt;STRONG&gt;same fields&lt;/STRONG&gt; ( other than key fields ) , you can create a &lt;STRONG&gt;secondary index with those fields.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Pinaki&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Pinaki Mukherjee on Feb 10, 2009 5:56 AM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Feb 2009 04:55:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-tuning-for-update-statement/m-p/5093677#M1182329</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-02-10T04:55:43Z</dc:date>
    </item>
    <item>
      <title>Re: Performance tuning for UPDATE statement.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-tuning-for-update-statement/m-p/5093678#M1182330</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;Avoid  updating a complete row, use UPDATE+SET statement to update a single field&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/scn/wiki?path=/display/abap/performance" target="test_blank"&gt;https://www.sdn.sap.com/irj/scn/wiki?path=/display/abap/performance&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please check this link &lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04s/helpdata/en/6e/b4fe76e7d311d5995b00508b5d5211/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04s/helpdata/en/6e/b4fe76e7d311d5995b00508b5d5211/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Feb 2009 08:11:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-tuning-for-update-statement/m-p/5093678#M1182330</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-02-10T08:11:15Z</dc:date>
    </item>
    <item>
      <title>Re: Performance tuning for UPDATE statement.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-tuning-for-update-statement/m-p/5093679#M1182331</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; then it is allways better specify all records of the table in sorted manner.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;really, I doubt that it will have any effect.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Feb 2009 09:53:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-tuning-for-update-statement/m-p/5093679#M1182331</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-02-10T09:53:03Z</dc:date>
    </item>
  </channel>
</rss>

