RE: Optimizer not using histogram to calculate estimated number of rows?

I wouldn't consider "over 100 rows" vs "3 rows" to be "highly skewed" in 
relation to a total of 166,067 rows.  You're talking about .0006% of the table 
vs. .0018% of the table - a very small percentage either way, and .0018%, or 
100 rows, probably isn't nearly enough to warrant a full scan instead of an 
index scan if that's what you have in mind.  Is that what you had in mind?

You might want to test with a FULL() hint to see just how much worse the 
performance is with a full scan.

Regards,
Brandon

________________________________
Privileged/Confidential Information may be contained in this message or 
attachments hereto. Please advise immediately if you or your employer do not 
consent to Internet email for messages of this kind. Opinions, conclusions and 
other information in this message that do not relate to the official business 
of this company shall be understood as neither given nor endorsed by it.

Other related posts: