<?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 performance affect due to sequential access in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-affect-due-to-sequential-access/m-p/1821188#M350950</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;     We are facing a performance problem in our system. we are running program with select statement with proper indexing followed but still it is showing as a sequential read in SM50. This is happening for SAP std programs also.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;   Database statistics are also updated last week.Why still it is showing as a sequential read. Most of the large tables shows sequential read only.  whether it can relate to memory or any other issues.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Karthik.k&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 11 Jan 2007 06:23:16 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-01-11T06:23:16Z</dc:date>
    <item>
      <title>performance affect due to sequential access</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-affect-due-to-sequential-access/m-p/1821188#M350950</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;     We are facing a performance problem in our system. we are running program with select statement with proper indexing followed but still it is showing as a sequential read in SM50. This is happening for SAP std programs also.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;   Database statistics are also updated last week.Why still it is showing as a sequential read. Most of the large tables shows sequential read only.  whether it can relate to memory or any other issues.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Karthik.k&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Jan 2007 06:23:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-affect-due-to-sequential-access/m-p/1821188#M350950</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-11T06:23:16Z</dc:date>
    </item>
    <item>
      <title>Re: performance affect due to sequential access</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-affect-due-to-sequential-access/m-p/1821189#M350951</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI Karthik!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SM50 is not a proper tool for analyzing select statements. Either only primary key, maybe also an access with unique secondary index will be displayed as direct access, the rest is counted as sequential - even if good secondary indices are used.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Make a SQL-trace (ST05) to check the access. Here you can see, which index (sometimes even with no. of index fields) is used. If this looks OK, don't worry about SM50. If you have bad accesses, check the source code and the actual filling of the select fields - even if all fields are programmed, not all are filled in a program all the time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Christian&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Jan 2007 07:46:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-affect-due-to-sequential-access/m-p/1821189#M350951</guid>
      <dc:creator>christian_wohlfahrt</dc:creator>
      <dc:date>2007-01-11T07:46:08Z</dc:date>
    </item>
    <item>
      <title>Re: performance affect due to sequential access</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-affect-due-to-sequential-access/m-p/1821190#M350952</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Use ST05 for SQL performance trace.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Jan 2007 11:30:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-affect-due-to-sequential-access/m-p/1821190#M350952</guid>
      <dc:creator>alex_m</dc:creator>
      <dc:date>2007-01-11T11:30:42Z</dc:date>
    </item>
  </channel>
</rss>

