InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comMon, 17 Jun 2013 23:13:02 GMT20http://www.sqlservercentral.com/Forums/Topic1403634-1549-1.aspx[quote][b]Kishore-132325 (1/7/2013)[/b][hr]but UPDATE STATISTICS with FULL SCAN will scan for the entire table everytime and unnecessary update stats even if its not needed. i ran a samle update stats with full scan on few of my dbs and its taken a very long time [ 8-9 hours ] to complete, also its very resource intensive.whereas when I run sp_updatestats, it works intelligently and just updates stats on those stats where its required, though it does for sample updates, but it coves more than 60% of my statistics.Thoughts ?[/quote]Just remember, the level of requirement for the sp_updatestats is just a single row being modified. It's not that sophisticated a piece of code. You could follow Gail's advice and use the same approach.Wed, 09 Jan 2013 04:50:37 GMTGrant Fritcheyhttp://www.sqlservercentral.com/Forums/Topic1403634-1549-1.aspx[quote][b]Kishore-132325 (1/7/2013)[/b][hr]but UPDATE STATISTICS with FULL SCAN will scan for the entire table everytime[/quote]Yup, that's what you need for accurate stats. You can run full scans on more important tables and sampled on less if you like. Not hard to add into a script if you know your tables well[quote]and unnecessary update stats even if its not needed. [/quote]Then you can just do a check against sysindexes (yes, the deprecated one) for rowmodctr > 0 and only update those. That's all that sp_updatestats does.Mon, 07 Jan 2013 10:31:33 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1403634-1549-1.aspxbut UPDATE STATISTICS with FULL SCAN will scan for the entire table everytime and unnecessary update stats even if its not needed. i ran a samle update stats with full scan on few of my dbs and its taken a very long time [ 8-9 hours ] to complete, also its very resource intensive.whereas when I run sp_updatestats, it works intelligently and just updates stats on those stats where its required, though it does for sample updates, but it coves more than 60% of my statistics.Thoughts ?Mon, 07 Jan 2013 09:45:41 GMTKishore-132325http://www.sqlservercentral.com/Forums/Topic1403634-1549-1.aspxDon't use sp_updatestats, it does sampled updates (unless you tell it otherwise). If you are doing a maint plan to manage stats, run the stats updates with fullscan.Mon, 07 Jan 2013 08:14:25 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1403634-1549-1.aspxhello - i have bi-monthly maintenance plan that re-builds all the indexes of my databases where fragementation > 5%. my indexes are in good shape with this frequency.However, with the re-build of indexes, my statistics only for those indexes are updated when the indexes are rebuilt. Also, i have auto-stats and create stats on [ default options ].But my other statistics are not getting updated.Is is a good idea to run sp_updatestats for all my user dbs after the rebuild index job completes. This will make sure all my other stats that need a update will also be updated and since my re-indexing job will update stats for those indexes, sp_updatestats will not touch them since they have just been rebuilt by the rebuild index job.So, basically, 2 steps:1. Run rebuild index job for all Dbs for frag > 5%2. Run sp_updatestats for all dbs.please suggest on the approach,.ThanksKMon, 07 Jan 2013 08:08:47 GMTKishore-132325