Re: Oracle Myths- Tablespace placement answered by Oracle

"Nuno Souto" <nsouto_at_optushome.com.au.nospam> wrote in message news:3ce510a9$0$15144$afc38c87_at_news.optusnet.com.au...
>
> > Even without concurrency in the strictest sense it is still
beneficial to
> > put the indexes and data on different disks. The above info
relates to one
> > query. There is nothing to stop multiple queries against the same
rows and
> > indexes from processing concurrently.
> >
> > So yes, you can get performance benefit by splitting the data and
indexes
> > onto different disks."
> >
>
>
> call me a dreamer, but if you put tables and indexes in same
tablespace
> and spread that tablespace over a number of devices you get EXACTLY
the
> same result as above.

You need to look down at the disk heads. If we're issuing zillions of single I/O's, that's a considerably different profile than zillions of I/O's that have some multi_block influence.

--
Pablo Sanchez, High-Performance Database Engineering
mailto:pablo_at_hpdbe.com
http://www.hpdbe.com
Available for short-term and long-term contracts