Re: Separating data, index objects

> 1. The table was loaded by an import, so has all blocks contiguous
> (well, in a few chunks from what I've seen), then the index was created
> in another tablespace.
>
> 2. The table was loaded by a process that added each row and its index
> within discrete transactions, and the index is in the same tablespace.
>
> It would seem to me #1 would have a higher desired information density,
> or at least the multiblock read would have a higher chance of not
> wasting time on an index block.

Actually there is no such thing as "all blocks contiguous." As amazing as it may be many operating systems won't lay down a single file on a clean drive that way.

We could talk about RAW but that is quite a different matter. And even on your single user database ... there will be a substantial amount of recursive SQL. In Oracle you are never alone.

-- 
Daniel A. Morgan
http://www.psoug.org
damorgan_at_x.washington.edu
(replace x with u to respond)