Re: Oracle Myths

Well, I read through the archived messages, and discovered that either half the Oracle experts don't know what they're talking about, or that half the Oracle experts know what they are talking about. The other half aren't talking. Anyway, I posted the question to Metalink, so we'll see what the consensus of the Oracle cube-dwellers is. Too bad there's no SQL standard related to this problem- if there was we could count on a definitive answer, or at least one from Joe Celko.

Best to extract tongue from cheek now, lest I get myself into trouble...

"Daniel Morgan" <dmorgan_at_exesolutions.com> wrote in message news:3CE288A2.8C816115_at_exesolutions.com...
> Niall Litchfield wrote:
>
> > Suggested list to be added to, deleted from etc
> >
> > Store your segments in one extent for optimum performance.
> > Space in an index is never reused.
> > Full table scans are always bad: use the index.
> > Seperate tables and indexes for performance reasons.
> > You should always backup the online redo logs to avoid data loss.
> > Buffer cache hit ratio should be as high as possible preferably greater
than
> > 90%.(from the java tool we use developed in house)
> > Library Cache hit ratio should be greater than 99% if it isn't increase
the
> > size of the shared pool.(ditto!)
> > Smallest table should be the driving table for hash joins.
> > PCTIncrease should be as small as possible but non-zero to minimize
> > tablespace fragmentation.1% is a good value (from my OCP course notes
though
> > not necessarily given by the tutor!)
> >
> > --
> > Niall Litchfield
> > Oracle DBA
> > Audit Commission UK
> > *****************************************
> > Please include version and platform
> > and SQL where applicable
> > It makes life easier and increases the
> > likelihood of a good answer
> >
> > ******************************************
>
> Thanks. I am going to get on the first one and see what I can determine.
>
> Daniel Morgan
>
Received on Thu May 16 2002 - 15:01:15 CDT