Re: Pin a table in memory

Roger Snowden wrote:
>
> Sometimes when you want something, you want it *now*. The ability to pin a
> table in cache is very much a performance technique. You have to consider
> the architecture of the application in question before you can determine
> the usefulness of pinning a table.
>

When you pin a table using ALTER TABLE <tablename> CACHE, does it cache the table immediately or does it only pin the rows in the table as they are selected? I assume that the indexing is cached as well, but can anyone verify this? I currently have some small static tables (and indexes) stored in a separate tablespace (and disk drive), but I am considering pinning these in memory and moving them to the same tablespace as our dynamic tables. Since the static tables are pinned in memory and rarely updated, I should only see I/O contention when the pinned tables are first loaded into the cache. Right? Any comments are welcome.

Vince Received on Wed Jan 29 1997 - 00:00:00 CST