Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Which buffering option will suit the best?

Hello

Table has a size of 200K records. Records are updated daily.

Table is used for look-up search.

Which buffering approach would you recommend?

Does single record buffering have any benefit?

Former Member
Former Member replied

Table has a size of 200K records. Records are updated daily.

Please keep in mind that each application server has its own table buffer. Whenever updates to a buffered table occurs, those updates appear delayed on other application servers. How often table buffers are synchronized is defined via profile parameter <em>rdisp/bufreftime</em>, default is every 120s. Might be irrelevant in your case, but it's good to keep it in mind.

Table is used for look-up search. Which buffering approach would you recommend?

Well, as you can see from the previous postings, there can be some general recommendations, but based on the facts you've posted it's impossible to tell if there even should be any buffering. I.e. if you do the look-up within a program that runs once then you shouldn't buffer the table via data dictionary settings, but simply buffer it within your program.

It is unclear how many of the 200k records are really used for look-ups and also what percentage of the data is updated. Also, row size matters.

In the end probably you'll be the only one able to judge the impact of the buffering. OSS note [1011158 - Table buffering on a SAP instance|https://service.sap.com/sap/support/notes/1011158] is also a good starting point. As always, there's also plenty of other documentation in the SAPhelp for table buffering.

0 View this answer in context

Helpful Answer

by
Not what you were looking for? View more on this topic or Ask a question