Query Tuning: CBO chooses a Full table Scan over the available indexes and doesn't recommend a new index to be built
Posted on 2003-11-24
I have a query that performs an inner join on 2 large files and has a condition or two in the where clause. When I run this query the optimizer checks the applicable indexes and choose to perform a Full Table Scan over using any of these indexes. For some reason or another it doesn't suggest an index to be built to avoid the table scan.
Any ideas on how I can get the optimizer to use an index? Or even how I can get it to suggest a index to be built?