Timeline for Update statistics for all databases all tables in a server
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 31, 2014 at 19:29 | comment | added | Kenneth Fisher |
Actually I believe she mentioned sp_updatestats at the bottom. Her main problem was the FULLSCAN which isn't happening in either case. Watch out for #2 though, you never know when things are going to change. It's always best to code for what's possible not what is right now. Although I'll admit I don't always manage it myself.
|
|
| Oct 31, 2014 at 19:24 | comment | added | Marcello Miorelli | regarding #3 I was following the an article by Brent Ozar you can see here: brentozar.com/archive/2014/01/… | |
| Oct 31, 2014 at 18:59 | comment | added | Aaron Bertrand | Right, I tried to address that in my answer, too. It can be like whack-a-mole. | |
| Oct 31, 2014 at 18:58 | comment | added | Kenneth Fisher | @AaronBertrand I wasn't aware of that. I'll keep in in mind in the future. Although to be fair her complaint (in that post) is that it updates tables that maybe shouldn't be because only a few rows (or even 1) have been modified. This solution is updating every table regardless, so I'm not sure it matters much. | |
| Oct 31, 2014 at 18:48 | comment | added | Aaron Bertrand | FWIW Erin Stellato repeatedly pushes people away from sp_updatestats. See sqlperformance.com/2013/07/sql-statistics/statistics-updates, for example. | |
| Oct 31, 2014 at 18:42 | history | answered | Kenneth Fisher | CC BY-SA 3.0 |