buffering the table

[Former Member]

guyz!

hope this post finds u all at high on spirit. over here, i am having a requirement to buffer one custom table. let me give the scenario of table access. here it goes:

1. it gets updated every month.

2. after getting updated, it is accessed.

3. i also believe that, table size is also small, i.e. size category = 0.

4. finally the access is like, mostly it will retreive only one month data, by taking all the key fields. in my case there are 5 key fields.

so can any one suggest me, which buffering type to use.

manas

[Former Member]

Hi manas,

1. i don't think buffering is required.

regards,

amit m.

[Laxmana_Appana_]

Hi,

select 'Buffering not allowed ' button for mentioned case.

Check this help:

Buffering status

Definition

The buffering status specifies whether or not a table may be buffered.

This depends on how the table is used, for example on the expected volume of data in the table or on the type of access to a table. (mainly read or mainly write access to the table. In the latter case, for example, one would not select buffering).

You should therefore select

- Buffering not allowed if a table may not be buffered.

- Buffering allowed but not activated if buffering is

principally allowed for a table, but at the moment no buffering

should be active. The

buffering type specified in this case is only

a suggestion.

- Buffering allowed if the table should be buffered. In this

case a buffering type

must be specified.

The buffering type defines whether and how the table should be buffered.

There are the following types of buffering:

single-record buffering

generic area buffering

full buffering

In generic area buffering, a number of key fields between 1 and no. of key fields-1 must be specified.

Regards

Appana

[Former Member]

Hi,

since it is small table since <i>size category = 0</i>.

and Don't do any thing for Buffering. Don't change any default settings. No need of Buffering in your case.

Regards

vijay

[Former Member]

Hi,

Buffering will increase the performance of the table.

If a table is accessed frequently, but all accesses are read accesses, this value can be exceeded.

For larger tables where large numbers of records are frequently accessed. However, if the application program is able to formulate an extremely selective WHERE condition using a database index, it may be advisable to dispense with full buffering.

For tables with frequent accesses to data not contained in the table. Since all records are contained in the buffer, a quick decision can be made as to whether or not the table contains a record for a specific key.

When considering whether a table should be fully buffered, you should take three aspects into account: the size of the table, the number of read accesses, and the number of write accesses.

<b>Tables best suited to full buffering are small, frequently read, and rarely updated.</b>

Regards,

Rajesh