Hmm, how about creating more filtered statistics exactly on the problematic ranges?
Or, tackling this from the other end, using OPTIMIZE FOR in the query and specifying a good range (or perhaps UNKNOWN)?
No comments:
Post a Comment