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

Home -> Community -> Mailing Lists -> Oracle-L -> RE: full-scan vs index for "small" tables

RE: full-scan vs index for "small" tables

From: Laimutis Nedzinskas <Laimutis.Nedzinskas_at_landsbanki.is>
Date: Wed, 28 Jun 2006 15:11:24 -0000
Message-ID: <5A8896FB2AFC5445A7DCFC5903CCA6B02CA2AF@W03856.li01r1d.lais.net>

 

> On Behalf Of Cary Millsap
> RBO is dramatically inferior to CBO in every case except for the one
where the operational manager doesn't do a good job of making sure that the statistics are a reasonable representation of the production data.

OK. To clarify my point:

Case1: In the world where sql developer says literally "a man must not have to think" CBO is a right thing. Let the software think.

Case2: in the world "do once and forget" I need stable sql plans. The "operational manager doesn't do a good job" does not work here. There is no problem to build even simple counter cases when CBO goes astray. What sql developer best practices would be then?

To the previous list I can think of to add one more: - bundle "good" statistics into your product setup.

Fyrirvari/Disclaimer
http://www.landsbanki.is/disclaimer

--
http://www.freelists.org/webpage/oracle-l
Received on Wed Jun 28 2006 - 10:11:24 CDT

Original text of this message

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