Re: Index tablespace

Depends on what style of RAID you have.

if you have banks of RAID devices ( doesnt sound like it from the original post ) then it is good to have seperate index space for each interrupt in the RAID controller, otherwise if you have RAID 5 it doesnt matter.

If you have RAID other than 5, you might gain something by striping and managing across the device in some fancy way, my experience shows this to be minimal, a good effort on tuning queries will be more worth the time.

hth
Randy

Allen wrote:
>
> Yes, but what if you have a raid device? There should be no difference in
> performance
> it that case.
>
> Edwin Esser wrote:
>
> > Putting the indexes in a seperate tablespace can come in very handy when you
> > put that tablespace on a different disk. That way when you do a query, the
> > index will be accessed through disk 1, the table itself on disk 2 => better
> > performance through better response times.
> >
> > Edwin
> >
> > "Alex Yevzelman" <yevz0001_at_tc.umn.edu> wrote in message
> > news:3815E9F2.4EF2619B_at_tc.umn.edu...
> > > I am wondering, what are the advantages and disadvantages of having a
> > > separate tablespace for indexes.
> > > We are converting an MS Access aplication that has ~80Mb and growing of
> > > data into Oracle 8i. Also, we are developing an application, which will
> > > have ~10Mb of data.
> > > I created a tablespace for each of these applications.
> > >
> > > Should I create a separate tablespace specifically for indexes or should
> > > I keep indexes together with the other schema object in each of the
> > > corresponding tablespaces?
> > > What are the general guidelines for this type of problem?
> > >
> > > Thanks.
> > > Alex.
> > >
Received on Tue Oct 26 1999 - 14:06:26 CDT