Tables that are frequently read during production use, but only rarely modified, such as those containing configuration data, should be buffered on the application server. The access to data in a buffered table is 10-50 times faster than accessing data in a non-buffered table, being read from the database cache. In the technical settings of a table in transaction SE11, you are able to turn on the table buffering and select the buffer type (fully buffered, generically buffered, or single record buffering).
In the following diagram it is depicted, how delivery class, data class, and buffering should be combined for (most of) the tables in your system.
Examples on how to read this diagram:
- delivery class C (customizing table) should not be combined with data class APPL1 (transactional data)
- a table that contains configuration data (APPL2), and which is assigned to delivery class S (system table), should be buffered
- a master data table (APPL0) with delivery class A (application table) should not be buffered, except if it has only a few entries (size category 0, or single record buffered with size category 0, 1, or 2)
Refer http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/25444 for more details.
No comments:
Post a Comment