<?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 on mass insert in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-on-mass-insert/m-p/6733993#M1457526</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;Why are you lock entry that not in the system ? &lt;/P&gt;&lt;P&gt;Normally we lock entry to prevent another people to acces to this information.&lt;/P&gt;&lt;P&gt;But in your case, you are alone to have data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any row of your internal table are store in DB before ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rgds&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 26 Feb 2010 14:40:51 GMT</pubDate>
    <dc:creator>StMou</dc:creator>
    <dc:date>2010-02-26T14:40:51Z</dc:date>
    <item>
      <title>performance on mass insert</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-on-mass-insert/m-p/6733989#M1457522</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hiii&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is the best way to do mass insert in a custom database table&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LOOP ITAB ENQUEUE ENDLOOP&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MASS INSERT table from ITAB&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LOOP ITAB DEQUEUE ENDLOOP&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note: can there be a performance issue doing it that way? since there are two loop&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Feb 2010 11:30:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-on-mass-insert/m-p/6733989#M1457522</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-02-26T11:30:52Z</dc:date>
    </item>
    <item>
      <title>Re: performance on mass insert</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-on-mass-insert/m-p/6733990#M1457523</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;use&lt;/P&gt;&lt;P&gt;ENQUEUE&lt;/P&gt;&lt;P&gt;INSERT ZTABLE FROM TABLE IT_TABLE.&lt;/P&gt;&lt;P&gt;IF SY-SUBRC IS INITIAL.&lt;/P&gt;&lt;P&gt;COMMIT WORK.&lt;/P&gt;&lt;P&gt;ENDIF.&lt;/P&gt;&lt;P&gt;DEQUEUE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Sachin Bidkar on Feb 26, 2010 1:23 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Feb 2010 12:07:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-on-mass-insert/m-p/6733990#M1457523</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-02-26T12:07:33Z</dc:date>
    </item>
    <item>
      <title>Re: performance on mass insert</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-on-mass-insert/m-p/6733991#M1457524</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;please note that here the enqueue i am not locking the whole table but will be locking only the entries data that i am inserting&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Feb 2010 12:47:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-on-mass-insert/m-p/6733991#M1457524</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-02-26T12:47:37Z</dc:date>
    </item>
    <item>
      <title>Re: performance on mass insert</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-on-mass-insert/m-p/6733992#M1457525</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;But this is the standard practice what i mentioned and what i understood and as per information..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Sachin Bidkar on Feb 26, 2010 1:51 PM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Sachin Bidkar on Feb 26, 2010 1:52 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Feb 2010 12:51:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-on-mass-insert/m-p/6733992#M1457525</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-02-26T12:51:27Z</dc:date>
    </item>
    <item>
      <title>Re: performance on mass insert</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-on-mass-insert/m-p/6733993#M1457526</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;Why are you lock entry that not in the system ? &lt;/P&gt;&lt;P&gt;Normally we lock entry to prevent another people to acces to this information.&lt;/P&gt;&lt;P&gt;But in your case, you are alone to have data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any row of your internal table are store in DB before ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rgds&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Feb 2010 14:40:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-on-mass-insert/m-p/6733993#M1457526</guid>
      <dc:creator>StMou</dc:creator>
      <dc:date>2010-02-26T14:40:51Z</dc:date>
    </item>
    <item>
      <title>Re: performance on mass insert</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-on-mass-insert/m-p/6733994#M1457527</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Case 1:&lt;/P&gt;&lt;P&gt;INSERT implies you are pushing new records into your table. In this case you don't have to lock entry by entry and INSERT data into your table. This hampers the performance.&lt;/P&gt;&lt;P&gt;Case 2:&lt;/P&gt;&lt;P&gt;If you are handling an existing record in table, then you must use MODIFY. This statement will over write the existing records with your changes and if a record is not found, it would create a new entry in your table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If either cases, its better to ENQUE, then do a mass update to table. Then,&lt;/P&gt;&lt;P&gt;if sy-subrc eq 0.&lt;/P&gt;&lt;P&gt;COMMIT WORK.&lt;/P&gt;&lt;P&gt;else.&lt;/P&gt;&lt;P&gt;ROLLBACK.&lt;/P&gt;&lt;P&gt;endif.&lt;/P&gt;&lt;P&gt;then deque.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Kiran&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Feb 2010 14:53:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-on-mass-insert/m-p/6733994#M1457527</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-02-26T14:53:05Z</dc:date>
    </item>
  </channel>
</rss>

