Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Oracle's Myth: keep tables and indexes in separate tablespaces

Re: Oracle's Myth: keep tables and indexes in separate tablespaces

From: Hulse <hulse_kevin_at_yahoo.com>
Date: 13 Oct 2003 11:50:23 -0700
Message-ID: <16926526.0310131050.6fb6c720@posting.google.com>


"Howard J. Rogers" <hjr_at_dizwell.com> wrote in message news:<3f84f251$0$30614$afc38c87_at_news.optusnet.com.au>...
> Snid wrote:
>
> >
> > So I guess I can see why lots of people think that it's best to separate
> > indexes from tables. It doesn't mention that you should only separate them
> > for administration purposes mainly.
>
> Quite right. The advice is still there, in plain, unadorned incorrectness,
> in the performance tuning course notes for Oracle 9i (published in version
> 2.1 only a few weeks ago).
>
> Oracle are also responsible for promoting the myth that getting a segment
> into a single extent is good for performance; that PCTINCREASE 1 is a good
> idea to protect against fragmentation (it causes it); that ASSM has no
> costs; that tuning consists of getting a good buffer cache hit ratio. You
> name it, they've touted it.
>
> These days, they have TUSC to do that sort of thing for them.
  

     I'm curious. TUSC archives their presentations and make them freely available for download. So, can you point me to where they are still making such claims? I have worked with Rich directly and he's never suggested such things. Received on Mon Oct 13 2003 - 13:50:23 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US