Re: MaxDB cache pinning

Hi Steve,

Ad 2)
Short answer: no

Ad 1)
It is not a problem, but a 'trade-off'. The more space you reserver for table pinning, the less Data Cache space you have available for all other database objects, which means that the 'non-pinned' tables would get flushed out earlier.
Lets say you have a performance issue related to a certain database table. Before using table cache pinning, I would advise to first identify the responsible SQL statements via MaxDB 'Command Monitor' and 'Resource Monitor'. Once you have the SQL, you could try to find out, if the statement can be optimized/rewritten to select less data for the desired result (to achive better 'selectivity') or if a database index might help to achieve less table reads. If the problematic statement is a join across tables or views, maybe the optimizer statistics are outdated. Or, maybe you can even delete some data of that table (and archive it somewhere).
And then, yes, you can use 'table pinning', just beware not to pin too big tables or for the reason of poorly optimized SQL statements :-)

Thorsten