This mean that everytime when there is not a need for the system to fetch the data from the database tables.
During runtime, it creates some temporary memory and keeps that fetched records in a Buffer like things and next time when you try to fetch the data at run time, first it checks for the run time buffer is there or not. If it is there it takes the data from that buffer, instead of bring from database.
Concepts of buffering
We have 3 types of buffering.
There are the following types of buffering:
- single-record buffering
- generic area buffering
- full buffering
Single-record buffering should be selected when :
- 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.
- 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.
0 Comments