SQL Server Performance

Update Statistics on huge tables - best practice

Discussion in 'Other SQL Server Blogs around the Web' started by Anonymous, Oct 23, 2007.

  1. Anonymous New Member

    If you have valid indexes and they are maintained with regular schedule of reindexing to address fragmentation, then you can go with UPDATE STATISTICS on the tables that has frequent updates, say once in 2 days during the quiet time on the databases. During the performance monitoring exercise you should test by running DBCC FREPROCCACHE and not recommended on the production server though. In any case I would suggest to consider cost as disk IO, Memory, and CPU, among other things. In any case the...(<a href="http://sqlserver-qa.net/blogs/perftune/archive/2007/10/23/2558.aspx">read more</a>)<img src="http://sqlserver-qa.net/aggbug.aspx?PostID=2558" width="1" height="1">

Share This Page