<?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: BUFFER in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/buffer/m-p/2405646#M536230</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;see the concept of Buffering&lt;/P&gt;&lt;P&gt;We have 3 types of buffering&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are the following types of buffering:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;o single-record buffering&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;o generic area buffering&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;o full buffering&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Single-record buffering should be selected when :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;o For large tables where there are frequent single-record accesses (using SELECT SINGLE ...). The size of the records being accessed should be between 100-200 KB.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;o For comparatively small tables for which the access range is large, it is normally advisable to opt for full buffering. Only one database access is required to load such a table for full buffering,&lt;/P&gt;&lt;P&gt;while single-record buffering calls for a very large number of table accesses.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And also check this matter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Single-record buffering: Only the records of a table that are really accessed are loaded into the buffer&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Single-record buffering should be used particularly for large tables where only a few records are accessed with SELECT SINGLE. The size of the records being accessed should be between 100 and 200 KB.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Full buffering is usually more suitable for smaller tables that are accessed frequently. This is because only one database access is necessary to load such a table with full buffering, whereas several database accesses are necessary for single-record buffering.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check this link : &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/f7/e4c5a8a84a11d194eb00a0c929b3c3/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/f7/e4c5a8a84a11d194eb00a0c929b3c3/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points for useful Answers&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Anji&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 21 Jun 2007 07:45:30 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-06-21T07:45:30Z</dc:date>
    <item>
      <title>BUFFER</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/buffer/m-p/2405645#M536229</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;      A table is buffered. By select statement i dont want to get the data from table buffer. i want to get the data from database. how? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;THANK YOU&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASHOK KUMAR&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Jun 2007 07:43:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/buffer/m-p/2405645#M536229</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-21T07:43:45Z</dc:date>
    </item>
    <item>
      <title>Re: BUFFER</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/buffer/m-p/2405646#M536230</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;see the concept of Buffering&lt;/P&gt;&lt;P&gt;We have 3 types of buffering&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are the following types of buffering:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;o single-record buffering&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;o generic area buffering&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;o full buffering&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Single-record buffering should be selected when :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;o For large tables where there are frequent single-record accesses (using SELECT SINGLE ...). The size of the records being accessed should be between 100-200 KB.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;o For comparatively small tables for which the access range is large, it is normally advisable to opt for full buffering. Only one database access is required to load such a table for full buffering,&lt;/P&gt;&lt;P&gt;while single-record buffering calls for a very large number of table accesses.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And also check this matter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Single-record buffering: Only the records of a table that are really accessed are loaded into the buffer&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Single-record buffering should be used particularly for large tables where only a few records are accessed with SELECT SINGLE. The size of the records being accessed should be between 100 and 200 KB.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Full buffering is usually more suitable for smaller tables that are accessed frequently. This is because only one database access is necessary to load such a table with full buffering, whereas several database accesses are necessary for single-record buffering.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check this link : &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/f7/e4c5a8a84a11d194eb00a0c929b3c3/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/f7/e4c5a8a84a11d194eb00a0c929b3c3/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points for useful Answers&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Anji&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Jun 2007 07:45:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/buffer/m-p/2405646#M536230</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-21T07:45:30Z</dc:date>
    </item>
    <item>
      <title>Re: BUFFER</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/buffer/m-p/2405647#M536231</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;Use this&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;select &amp;lt;field&amp;gt; from &amp;lt;table&amp;gt; bypassing buffer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ameet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Jun 2007 07:47:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/buffer/m-p/2405647#M536231</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-21T07:47:55Z</dc:date>
    </item>
    <item>
      <title>Re: BUFFER</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/buffer/m-p/2405648#M536232</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can use the addition BYPASSING BUFFER  in the from clause of the select statement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;See the help on FROM command for more info...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Arun&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Jun 2007 07:49:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/buffer/m-p/2405648#M536232</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-21T07:49:34Z</dc:date>
    </item>
  </channel>
</rss>

