<?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 OPEN CURSOR vs Persistent class in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/open-cursor-vs-persistent-class/m-p/8634431#M1665190</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Expert,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; I want to update custom table containing more than 3 crore record. Please provide best development stratedgy to update so large record.&lt;/P&gt;&lt;P&gt;I am planning to use one of the following strategy&lt;/P&gt;&lt;P&gt;1. Open Cursor statement to break record in Smaller package size and update the record.&lt;/P&gt;&lt;P&gt;2 . Create a Persistent class for custome table, using trasactional service to break record&amp;nbsp; based on certain condition and then using Persistent by query method on those set and update the record.&lt;/P&gt;&lt;P&gt;Which one is better stratedgy to update the record ! &lt;/P&gt;&lt;P&gt;Is using Persistence class increase the performance on update task ? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Kapil.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 04 Apr 2012 11:51:32 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2012-04-04T11:51:32Z</dc:date>
    <item>
      <title>OPEN CURSOR vs Persistent class</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/open-cursor-vs-persistent-class/m-p/8634431#M1665190</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Expert,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; I want to update custom table containing more than 3 crore record. Please provide best development stratedgy to update so large record.&lt;/P&gt;&lt;P&gt;I am planning to use one of the following strategy&lt;/P&gt;&lt;P&gt;1. Open Cursor statement to break record in Smaller package size and update the record.&lt;/P&gt;&lt;P&gt;2 . Create a Persistent class for custome table, using trasactional service to break record&amp;nbsp; based on certain condition and then using Persistent by query method on those set and update the record.&lt;/P&gt;&lt;P&gt;Which one is better stratedgy to update the record ! &lt;/P&gt;&lt;P&gt;Is using Persistence class increase the performance on update task ? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Kapil.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Apr 2012 11:51:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/open-cursor-vs-persistent-class/m-p/8634431#M1665190</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2012-04-04T11:51:32Z</dc:date>
    </item>
    <item>
      <title>Re: OPEN CURSOR vs Persistent class</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/open-cursor-vs-persistent-class/m-p/8634432#M1665191</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please note that "crore" is not well known in Europe and the US, so you are limiting your responses.&lt;/P&gt;&lt;P&gt;It is not recommended to&amp;nbsp; use the persistence framework for mass processing of database records. Effectively you'd just be doing a load of select singles.&lt;/P&gt;&lt;P&gt;To read bulk data from the database, use OPEN CURSOR.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Apr 2012 12:15:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/open-cursor-vs-persistent-class/m-p/8634432#M1665191</guid>
      <dc:creator>matt</dc:creator>
      <dc:date>2012-04-04T12:15:21Z</dc:date>
    </item>
  </channel>
</rss>

