Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Bypassing Buffer

Former Member
0 Likes
1,504

What is the advantage of using "Bypassing Buffer" in select statement ?

Message was edited by:

tangirala sriram

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
1,173

bypassing buffer on the select statement when you need the most up-to-date information, for example, select * from ztxtlfa1 bypassing buffer. Doing so causes the buffer to be ignored and the data to be read directly from the database. You should use this whenever you are reading for update, that is, reading a record that will be updated and written back to the database.

5 REPLIES 5
Read only

Former Member
0 Likes
1,173

Hi

We have 3 types of buffering

There are the following types of buffering:

o single-record buffering

o generic area buffering

o full buffering

Single-record buffering should be selected when :

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.

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,

while single-record buffering calls for a very large number of table accesses.

And also check this matter.

Single-record buffering: Only the records of a table that are really accessed are loaded into the buffer

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.

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.

Check this link :

http://help.sap.com/saphelp_nw04/helpdata/en/f7/e4c5a8a84a11d194eb00a0c929b3c3/content.htm

reward if useful

regards

Anji

Read only

Bema
Active Participant
0 Likes
1,173

hi,

if you have set the buffer while creating the table,

select stmt will read the records from buffer.

If you don't want to read it from buffer , you can use ' bypass buffer' with select stmt.

Reward if helpful

Read only

Former Member
0 Likes
1,174

bypassing buffer on the select statement when you need the most up-to-date information, for example, select * from ztxtlfa1 bypassing buffer. Doing so causes the buffer to be ignored and the data to be read directly from the database. You should use this whenever you are reading for update, that is, reading a record that will be updated and written back to the database.

Read only

Former Member
0 Likes
1,173

Hi..

if u want to get the most updated data from database, which is not modified at present ( which is buffered...) use bypassing buffer..

Read only

Former Member
0 Likes
1,173

hi,

supose u got an table with is buffered one so when u read it first time sys will keeps the retrived data in buffer so that 2nd time u can cread directly from buffer without goin gto DB so increasing the performance suposse some one edit the table n entered new value so if u keep on reading from buffer u wil not get the new value for this u have to use BYPASSING BUFFER stm usally small tables will be buffered to incerease the perfomance.

reward if useful

ravi