table buffering

[Former Member]

if we buffer a table the performance will be improved and the data fetches from app server so that we need not to hit the database many times but if we see for vbak table buffering not allowed is checked why so ?can anyone explain me ?plz

[Former Member]

Hi,

If you use table buffering then you may get inconsistent entries from the buffer. The records fetched will not be up to date.

So you can use table buffering only for less frequently updated tables.

Regards

Wenceslaus

[dev_parbutteea]

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).

[Former Member]

well, like you can imagine table buffering means reading those records and store them in RAM.

This is done normally for cute small customizing tables.

Now vbak is a HUGE table, with about 200 columns.

Additionally there tend to be HEAPS of records in VBAK, so storing VBAK in your RAM will probably take up more space than your RAM is.

due to those reasosn it is forbidden to store VBAK or other huge tables like VBAK. E.G. MARA, MARC, EKPO, ...

[Former Member]

Buffering of tables will improve the performance but only for specific table, where the data is not huge. So buffering a Transaction table where you have many records is not a very good idea, buffering of most used Master data table is fine.

VBAK is a transactional data table, having loads of data, so it is not buffered. Hope it makes some sense

Regards,

Vishal