Table buffering in Technical settings

[former_member689077]

Hello experts,

Can any one explain me on which cases we are not using buffers? and on which cases we are using buffers?

• buffering not allowed
• buffering allowed
• buffering allowed but switched off

please explain with certain scenarious

[FredericGirod]

(for Oracle, I am not sure about Hana)

If you set a table as buffered, and you put a SQL trace on a SELECT SINGLE, you will see SAP doing a FULL access to the database. Put everything in the memory and working only from memory.

All the next SELECT statement will work in the memory, until the data is change in the table. At this moment, SAP will do again a FULL access.

So.

Never put a table frequently change as buffered.

If a table is set as buffered, but you change this data, switch off the buffer

There is a limite on the memory size, so do not put ALL the table as buffered, because when there is no more space, old buffered table are cleaned from the memory and the futur SELECT will do a Full access.

[former_member689077]

Thank you

[jmodaal]

Hello,

this can be a complex topic. Have a look at SAP note 1011158 for a first step. It is more about customer tables, but the mentioned rules are valid in general. Same for the description of how to check whether tables should be buffered or not.

[former_member1716]

veera1234,

Buffering improves the performance of table when accessing the records of the table.

On a short note only transparent tables and pool tables can be buffered, cluster table cannot be buffered. To have a complete understanding kindly go through the below link:

TABLE BUFFERS

Regards!

[Sandra_Rossi]

It's explained in the ABAP documentation, in the SAP library, in the forum, etc. What didn't you understand well?