Re: cache table vs. indexed table, and multiblock reads

Just remembered,

I put some stuff about cache etc. on my website a couple of weeks ago. There are big changes from V7 to V8 on how you are supposed to handle objects with different aging characteristics.

--

Jonathan Lewis
Yet another Oracle-related web site: www.jlcomp.demon.co.uk

>Sweth Chandramouli wrote:
>
>> 1) when would it make sense to use a cache table versus
>> a fully indexed one? as i understand it, the main advantage of
>> a cache table is that it disables buffer aging, so that small
>> lookup tables that are read via full-table-scans will be read
>> into the buffer cache like regular data, instead of being placed
>> at the "old" end of the stack, so that it will be overwritten
>> immediately. fully indexing a table, on the other hand, prevents
>> the full table scan from ever happening, but is mostly useful for
>> the same sorts of tables. how should i pick between the two?
>>
Received on Thu May 06 1999 - 14:16:49 CDT