Re: Table growth - disk sizing

On 8/23/05, Ranko Mosic <ranko.mosic@xxxxxxxxx> wrote:
> so there is no precise control over
> file location on disk. Why separate objects into tablespaces/datafiles
> when you don't know where read/write is going to end up anyway ?
> 
> Ranko.

I agree that separating indexes and tables to avoid head contention is
not worthwhile in a RAID environment.  However, there are other good
reasons to do so.  It  makes object management and recovery much
easier.

"Hot spots" --- I've heard that some types of hot spots can be avoided
by setting up indexes in descending order.  I'm not sure that I
followed the agrument completely and if anyone would like to jump in
here with an explanation I'd love to read it.
--
http://www.freelists.org/webpage/oracle-l

Other related posts: