<?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: Logical Dbase Performance in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/logical-dbase-performance/m-p/4627728#M1090011</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Solved by using batch processing&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Oct 2008 11:55:59 GMT</pubDate>
    <dc:creator>former_member426550</dc:creator>
    <dc:date>2008-10-15T11:55:59Z</dc:date>
    <item>
      <title>Logical Dbase Performance</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/logical-dbase-performance/m-p/4627725#M1090008</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi fellow programmers..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i developed a payroll program which work fine at the development server..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;upon transport to QAS server..i noticed that the program is not performing well when dealing with large number of data..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i also tried running it with minimal data(2K records) at qas server and works fine since i applied most of the performance tunning guide... &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;is there any way to prevent this?when i debug it i found out that for 1-3k records the program is doing well, but upon reaching 4k records above, the program is running slow.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;my plan is to divide the data by 2k so that from start of execution to finish, the program will run fast...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;any other approach?or any suggestions?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks for reading..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Oct 2008 14:16:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/logical-dbase-performance/m-p/4627725#M1090008</guid>
      <dc:creator>former_member426550</dc:creator>
      <dc:date>2008-10-09T14:16:03Z</dc:date>
    </item>
    <item>
      <title>Re: Logical Dbase Performance</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/logical-dbase-performance/m-p/4627726#M1090009</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;PY extraction data is long lasting process. If you run it for so huge population it will extend even more. I usually don't bother how long it will take (someone else will run it anyway;) ). Normally user can provide not the population itself but PY area or personal area instead (so the report would run couple times but faster). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is to be noticed here is that you may reach timeout as run time will be too long. I suggest to use FM SAPGUI_PROGRESS_INDICATOR in order to avoid such situation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Marcin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Oct 2008 14:24:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/logical-dbase-performance/m-p/4627726#M1090009</guid>
      <dc:creator>MarcinPciak</dc:creator>
      <dc:date>2008-10-09T14:24:49Z</dc:date>
    </item>
    <item>
      <title>Re: Logical Dbase Performance</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/logical-dbase-performance/m-p/4627727#M1090010</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;what i did is create another program then used submit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;get pernr.&lt;/P&gt;&lt;P&gt;add 1 to ctr.&lt;/P&gt;&lt;P&gt;gt_pernr-low = p0001-pernr.&lt;/P&gt;&lt;P&gt;append gt_pernr.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if  ctr eq 30.&lt;/P&gt;&lt;P&gt;submit payroll with gt_pernr.&lt;/P&gt;&lt;P&gt;endif. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;by doing this was able to control the payroll program to process 30 employees only  ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;save running time by 20-30 percent..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Oct 2008 11:54:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/logical-dbase-performance/m-p/4627727#M1090010</guid>
      <dc:creator>former_member426550</dc:creator>
      <dc:date>2008-10-15T11:54:57Z</dc:date>
    </item>
    <item>
      <title>Re: Logical Dbase Performance</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/logical-dbase-performance/m-p/4627728#M1090011</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Solved by using batch processing&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Oct 2008 11:55:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/logical-dbase-performance/m-p/4627728#M1090011</guid>
      <dc:creator>former_member426550</dc:creator>
      <dc:date>2008-10-15T11:55:59Z</dc:date>
    </item>
  </channel>
</rss>

