03 January 2011
Experienced DBAs know that auto-update-stats is not sufficient to keep statistics updated on large tables. This is doubly true for tables where the DML activity is near one end of the clustered key.
There are some common workarounds:
Not content with any of these, I’ve gone ahead and built my own script:
Now I can run this script on a near-constant schedule, and it will update each table as soon as a configurable percentage of rows or number of rows have changed. You can also configure the sampling percentages. I think it is The New Hotness very useful.
Coming up next: A version that compensates for filtered indexes & filtered statistics.