Leeland (9/24/2012)
I had thought that if the query (which has the two filters in the WHERE) had a covering NC index that it would bypass the creation of those system generated stats...
Except that neither of the indexes you created is at all useful for that query. Technically covering, not none were seekable.
What I am getting out of your comment is that the only way to avoid having those system generated stats is to have a NC index for each column in the predicate...is that correct?
Yes, but that's not a very good indexing strategy. Why are you trying to avoid those stats? There's little downside in having them
In your experience with updating stats...how much of an impact is it in comparison to running something like a index rebuild?
Impact, not all that much usually. Depends on the settings though (sampled vs full scan)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability