Re: full-scan vs index for "small" tables
- From: "Niall Litchfield" <niall.litchfield@xxxxxxxxx>
- To: "Wolfgang Breitling" <breitliw@xxxxxxxxxxxxx>
- Date: Fri, 30 Jun 2006 10:31:20 +0100
That's true, but I can't really believe that anyone would want each
and every piece of SQL in the database, including all the dictionary
stuff, to use an index always. Could they?
Niall
On 6/30/06, Wolfgang Breitling <breitliw@xxxxxxxxxxxxx> wrote:
Except that it is impractical/impossible to adorn each and every sql
with such a hint.
At 11:37 PM 6/29/2006, Niall Litchfield wrote:
>On 6/30/06, Mladen Gogala <gogala@xxxxxxxxxxxxx> wrote:
>>It's not indeterministic, but is extremely complex and its very
>>hard to predict
>>the output. What I really need is a "use an index if it exists"
>>parameter that
>>Oracle doesn't want to give us.
>
>That sounds rather like the /*+ INDEX table_alias(colum list) */ hint
>that is available with 10.1 and above to me.
>--
>Niall Litchfield
>Oracle DBA
>http://www.orawin.info
Regards
Wolfgang Breitling
Centrex Consulting Corporation
www.centrexcc.com
--
Niall Litchfield
Oracle DBA
http://www.orawin.info
--
http://www.freelists.org/webpage/oracle-l
- Follow-Ups:
- Re: full-scan vs index for "small" tables
- From: Connor McDonald
- References:
- RE: full-scan vs index for "small" tables
- From: Laimutis . Nedzinskas
- RE: full-scan vs index for "small" tables
- From: Wolfgang Breitling
- Re: full-scan vs index for "small" tables
- From: Mladen Gogala
- Re: full-scan vs index for "small" tables
- From: Niall Litchfield
- Re: full-scan vs index for "small" tables
- From: Wolfgang Breitling
Other related posts:
- » full-scan vs index for "small" tables
- » Re: full-scan vs index for "small" tables
- » Re: full-scan vs index for "small" tables
- » Re: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » Re: full-scan vs index for "small" tables
- » Re: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » Re: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » Re: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » Re: full-scan vs index for "small" tables
- » Re: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » Re: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » Re: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » Re: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » Re: full-scan vs index for "small" tables
- » Re: full-scan vs index for "small" tables
- » Re: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » Re: full-scan vs index for "small" tables
- » Re: full-scan vs index for "small" tables
- » Re: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » Re: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
- » Re: full-scan vs index for "small" tables
- » RE: full-scan vs index for "small" tables
Except that it is impractical/impossible to adorn each and every sql with such a hint.
At 11:37 PM 6/29/2006, Niall Litchfield wrote: >On 6/30/06, Mladen Gogala <gogala@xxxxxxxxxxxxx> wrote: >>It's not indeterministic, but is extremely complex and its very >>hard to predict >>the output. What I really need is a "use an index if it exists" >>parameter that >>Oracle doesn't want to give us. > >That sounds rather like the /*+ INDEX table_alias(colum list) */ hint >that is available with 10.1 and above to me. >-- >Niall Litchfield >Oracle DBA >http://www.orawin.info
Regards
Wolfgang Breitling Centrex Consulting Corporation www.centrexcc.com
- Re: full-scan vs index for "small" tables
- From: Connor McDonald
- RE: full-scan vs index for "small" tables
- From: Laimutis . Nedzinskas
- RE: full-scan vs index for "small" tables
- From: Wolfgang Breitling
- Re: full-scan vs index for "small" tables
- From: Mladen Gogala
- Re: full-scan vs index for "small" tables
- From: Niall Litchfield
- Re: full-scan vs index for "small" tables
- From: Wolfgang Breitling