Title: Message
Hi
there.
I have a non-unique
index on a table, and I'm trying to force Oracle to usethe index - but it
always does a FTS. Why? (I've tried it with and withoutthe
alias)
SQL set
autotrace traceonlySQL SELECT /*+ INDEX(A,vehicle_veh_year_indx) */
DISTINCT veh_year 2 FROM
Administrator Fairfield Resorts, Inc.
5259 Coconut Creek Parkway Ft. Lauderdale, FL, USA 33063
-Original Message-From: Cunningham, Gerald
[mailto:[EMAIL PROTECTED]]Sent: Friday, January 31, 2003
1:31 PMTo: Multiple recipients of list ORACLE-LSubject:
index hint ignored?
Hi
Of Cunningham,
GeraldSent: Friday, January 31, 2003 10:31 AMTo:
Multiple recipients of list ORACLE-LSubject: index hint
ignored?
Hi
there.
I have a
non-unique index on a table, and I'm trying to force Oracle to usethe
index - but it always does a FTS. Why? (I've tried
and returns the
quickest.
Dan
Fink
-Original Message-From: Cunningham, Gerald
[mailto:[EMAIL PROTECTED]]Sent: Friday, January 31, 2003
11:31 AMTo: Multiple recipients of list ORACLE-LSubject:
index hint ignored?
Hi
there.
I have a
non-unique index on a table
]; Cunningham,
GeraldSubject: RE: index hint ignored?
Hi
Jerry,
Methinks it's because this is a small table. 20
records? Peanuts. Why bother with the index.
On
the same token you should probably not spend a lot of time worrying about
this... unless this is just a learning exercise
Friday.
LK
-Original Message-From: Cunningham, Gerald
[mailto:[EMAIL PROTECTED]]Sent: Friday, January 31, 2003
2:32 PMTo: Koivu, Lisa; [EMAIL PROTECTED]Subject: RE:
index hint ignored?
Thanks, Lisa.
This
particular table is rather small (~20,000 rows, 1.3 Mb in size, 20
Title: Message
I've
tried it both ways, with the comma and without - same result.
-Original Message-From: K
Gopalakrishnan [mailto:[EMAIL PROTECTED]] Sent: Friday, January 31,
2003 2:13 PMTo: Multiple recipients of list
ORACLE-LSubject: RE: index hint ignored?
Hi
PMTo: Multiple recipients of list ORACLE-LSubject: RE:
index hint ignored?
Gerald,
Is veh_year a nullable column? If so, an index lookup may
give you incorrect results (nulls are not indexed), so a full table scan will
be used.
Of course, is a full table scan a bad choice? Don't
Title: Message
Try
Analyzing the table first and issue the select stmt.
--
Babu
-Original Message-From: Cunningham, Gerald
[mailto:[EMAIL PROTECTED]]Sent: Friday, January 31, 2003
11:56 AMTo: Multiple recipients of list ORACLE-LSubject:
RE: index hint ignored?
I've
Title: RE: index hint ignored?
Hmmm ... without where clause you are retrieving all rows ... how would you enforce index?
Try adding
where veh_year = veh_year ...
Raj
__
Rajendra Jamadagni MIS, ESPN Inc.
Rajendra dot Jamadagni at ESPN
recipients of list ORACLE-LSubject:
RE: index hint ignored?
Hi
Dan,
H. That's interesting. Yes, the column does allow nulls. Not sure
if there actually are any null values, I'll have to
check...
Thanks!
-
Jerry
-Original Message-From: Fink, Dan
-From: Cunningham, Gerald
[mailto:[EMAIL PROTECTED]]Sent: Friday, January 31, 2003
10:31 AMTo: Multiple recipients of list ORACLE-LSubject:
index hint ignored?
Hi
there.
I have a
non-unique index on a table, and I'm trying to force Oracle to usethe
index - but it always
PROTECTED]'
Onderwerp:index hint
Hi,
I'm on Oracle 7.3.4 HP-UX 10.20 and trying to get some queries working
again
on same performance after an index has been added in order to get around
possible
deadlocks because of use of a foreign key relation.
I tried adding an hint
Refer to aliases (in that case 'oa'), not tablenames, in hints.
Jeroen van Sluisdam wrote:
-Oorspronkelijk bericht-
Van: Jeroen van Sluisdam
Verzonden:donderdag 17 januari 2002 14:40
Aan: '[EMAIL PROTECTED]'
Onderwerp:index hint
Hi,
I'm on Oracle 7.3.4 HP-UX
change the hint to /*+ INDEX(oa I_OPTION_ALLOTMENTS_2) */
if the statement uses an alias for a table, then the hint must use the alias
too
hth,
Marin
...what you brought from your past, is of no use in your present. When
you must choose a new path, do not bring old experiences
Verzonden: donderdag 17 januari 2002 14:40
Aan: '[EMAIL PROTECTED]'
Onderwerp: index hint
Hi,
I'm on Oracle 7.3.4 HP-UX 10.20 and trying to get some queries working
again
on same performance after an index has been added in order to get around
possible
deadlocks because of use
Is there any difference between the FIRST_ROWS hint
(which is said to "generally force the use of indexes" - Niemiec)
and the use of the INDEX hint (without specifying a particular
index)?
Is something else going on behind the scenes with FIRST_ROWS or is this
gratuitous bloat that
17 matches
Mail list logo