Re: Index tablespace

From: Connor McDonald <connor_mcdonald_at_yahoo.com>
Date: Wed, 27 Oct 1999 21:30:05 +0800
Message-ID: <3816FE5C.6ABF@yahoo.com>

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.
> > >

RAID minimises to some degree the disk contention, but even better would be to have a RAID for data and a RAID for indexes... --

---

Connor McDonald
"These views mine, no-one elses etc etc" connor_mcdonald_at_yahoo.com

"Some days you're the pigeon, and some days you're the statue." Received on Wed Oct 27 1999 - 08:30:05 CDT