Re: Tablespaces and indexes

Hi Michiel,

itīs better to place indexes on separate tablespaces on separate disks! I/O will be much better if data and index do not reside on one disk. One potential alternative is to build a stripe set of as much disks as you can afford (but please remeber to mirror the set - a loss of one disk could cost your whole data otherwise) and put all tablespaces - data or index - on this stripe set. I/O will be equal on all disks and no single bottleneck will slow down your warehouse.

HTH
Andy

Michiel Brunt <mbrunt_at_inergy.nl> schrieb in im Newsbeitrag: 9ock03$6lj$1_at_scavenger.euro.net...
> We created a data warehouse with data spread over multiple tablespaces.
> Large tables have their own, others share a tablespace.
> In a book about database tuning I read that indexes should be placed in
the
> same tablespace as the table it is built on.
> However, I have heard others say it is better to store indexes in a
seperate
> index tablespace.
>
> Who can tell me what is best for performance?
>
> Thanks, Michiel
>
>
Received on Thu Sep 20 2001 - 07:13:00 CDT