Ninja's_RGR'us (6/27/2011)
Grant Fritchey (6/27/2011)
It really depends on the volatility of the data, the structure of the indexes, and the types of queries run against it. We updated statistics on an insurance system I used to manage nightly for most databases. A few were weekly. We even had one table that, due to very poor construction, had it's statistics updated with a full scan once every 15 minutes. So there's no one right answer.Full scan every 15 mintues????????????????
I sure hopre it didn't take 14 minutes to complete that scan :w00t:.
Ha! No, it took about 2 minutes though, but it was absolutely necessary. The data in the table would skew so badly and changed so frequently that if we didn't update the stats, we were almost guaranteed a bad execution plan 3-4 times a day due to bad parameter sniffing. It was messed up to say the least, but the constant update on the stats didn't hurt the system, it helped.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning