mike.hockman (9/18/2013)
In our bi-weekly Index rebuild job, I am immediately running sp_updatestats following the Index rebuild. I figured it was more efficiant this way.
That could actually be harmful. Index rebuilds update statistics. Running sp_updatestats afterwards can then update the stats with a sample and make the stats less accurate. I would recommend you remove that and replace it with an UPDATE STATISTICS <stats name> WITH FULLSCAN every day that you don't have an index rebuild running. If you need it more frequently on some tables, well I've heard of some cases where stats are updated on some tables every hour.
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