Buffer table for small customize table with approx 15k records

[Former Member]

Hi,

I have small customize table with approx 15k records.

MANDT    CLNT   3

ZDCR       CHAR 4

ZSTR        CHAR 4

MRPPP    CHAR 3

PLIFZ       DEC 3

above table is consider configuration table with minimum modification and very frequence access. I was thinking to set as buffer table.

Please advise whether reasonable and practical to set above table as buffer table.

Thank You and Best Regards

Fernand

[Former Member]

Hi,

I have small customize table with approx 15k records.

MANDT    CLNT   3

ZDCR       CHAR 4

ZSTR        CHAR 4

MRPPP    CHAR 3

PLIFZ       DEC 3

above table is consider configuration table with minimum modification and very frequence access. I was thinking to set as buffer table.

Please advise whether reasonable and practical to set above table as buffer table.

Thank You and Best Regards

Fernand

[former_member196490]

If the table data is not modified frequently but is accessed quite frequently you can consider setting the table as a buffer table

[Former Member]

see this rules for buffering the table

Thumb rules for table buffering in SAP « Diary of a Confused DBA…..

[Former Member]

HI

Depends on the situation as per your requirement 15k records buffering is good but the table data modifying frequently or accessing frequently that time its more better.

FYI just read the below data and links i hope u can understand.

Thumb rules for table buffering in SAP

Important points for buffering of Table:

• A buffered table does not use indexes and instead always under full table scan.
• Select statement with order by primary key only use buffer, any other order by condition bypass buffer.
• Big tables should not be buffered, use index instead.
• Table which has frequent operations (insert/update/delete) should not be buffered. If percentage of inserts /updates /deletes more than 20% of total access do not buffer the table. It causes additional I/O with database. This increases many times if there is more than one SAP dialogue instances (Application Servers).
• This is further depended on the parameters rdisp/bufrefmode and rdisp/bufreftime
• If a poorly performing partially buffered table is frequently accessed by index range scan, better option is to find a generic key and use of generic key buffering.

http://help.sap.com/saphelp_nw04/helpdata/en/cf/21f244446011d189700000e8322d00/frameset.htm

http://scn.sap.com/thread/687263

Regards

Mahesh

[HermannGahm]

>...and instead always under full table scan.

this is not true...

[HermannGahm]

Hi,

read this:

http://www.sap-press.de/download/dateien/259/sap_press_pog_007.pdf

Kind regards,

Hermann

[yuri_ziryukin]

Many very comprehensive answers above

I try to give a short answer: yes

255kb size is still ok. Few modifications and frequent accesses - all of them are reasons to buffer this table.

[HermannGahm]

good one Yuri:

Matthew 5:37

Instead, let your message be 'Yes' for 'Yes' and 'No' for 'No.' Anything more

than that comes from the evil one."

i agree.... yes 🙂

[Former Member]

Dear All, thank you very much for the answer.

Best Regards

Fernand