why do you think hitting the indexes is a bad thing? what is the
performance of this query? What's the explain plan?
--- Seema Singh [EMAIL PROTECTED] wrote:
Hi
I am executing following query adn this query hits a number of
indices on
this table.let me know what is wrong please.all in
Also do you know what is the most selective part of the query. If you know
that one index will bring back the fewest rows then try hinting to use it.
-Original Message-
Sent: Tuesday, July 23, 2002 5:59 PM
To: Multiple recipients of list ORACLE-L
why do you think hitting the indexes
Title: RE: Index performance
Seema,
It would really help to see your index scripts also. If you have an index that includes emp_id, reg_date, emp_st, last_access, emp_status, and match, that index should work best. Use a hint on that index.
You say that this query hits a number
The SQL appears to be fine.
If it uses too many indexes then perhaps all the indexes are on a single
column. Perhaps you need to create a concatenated index.
At any rate, if it runs too slowly, post the SQL again with an explain plan.
--
Please see the official ORACLE-L FAQ:
What is the selectivity of the columns emp_st, emp_status and match?
If there are just 3-4 distinct values in the column, do not use b-tree index
on them. Just drop the Indexes on those columns and try again. If still slow
then try bitmap indexes on those low selectivity columns.
Sanjay
