I've been looking at the explain plans on a 3-rd party package that we are
using. I see that every single query is using "table access by rowid
range" with 2 bind variables. Some of these queries have additional
"where" clauses, but those on indexed columns are always defeated because
of a function to the left of the operator, ie upper().
In looking at various examples in the Oracle docs about "table access by
rowid", all of the examples always have the "by rowid" working directly
with an index. Since this app is ignoring or defeating all of the indexes,
is there any performance difference between a full table scan and "by rowid
range"?
Received on Sat Sep 23 2000 - 09:37:12 CDT
