Of course, the worst case scenario would be if you first rebuild your indexes, which also updates the index statistics by scanning the entire table, and later you run UPDATE STATISTICS using the default values, which again updates the index statistics but this time only with a default and smaller sample.
Not only you are updating your index statistics twice but you are overwriting the better of the two choices.
Since the first job only updates index statistics and the second one only updates column statistics, it does not matter which one you execute first.
Some other more complicated scenarios include when you have jobs which rebuild your indexes based on their fragmentation level.
One of the questions I was asked recently while speaking at the Los Angeles SQL Server Professionals Group and the Orange County SQL Server User Group (*) was regarding the order in which jobs like rebuilding indexes or updating statistics should be executed as part of the database maintenance activities.
In general you should consider the following important points, focusing in the fact that there are two kinds of statistics: index and column statistics.
Benjamin has also been a speaker at many SQL Server conferences and events around the world including the PASS Summit, SQL Server Connections and SQLBits.
His blog can be found at he can also be reached on twitter at @Benjamin Nevarez.
My ticker and news feed are not updating, despite me logging out, clearing my cache, trying different browsers, et cetera.
Found a script that does fix the issue most of the time. Copy this to .vbs, run it on the client machine having issues.
Then restart the sms service and re-run your cycle (software update, etc).
Run again the query to verify that a new statistics object for the Product ID column has been created.
Notice the value of the auto_created column which tells if the statistics were automatically created by the query processor.4) Reorganizing an index, for example using the ALTER INDEX …