UPDATE STATISTICS against all user-defined and internal tables in the current database.
sp_updatestats [ [ @resample = ] 'resample' ]
Return code values
0 (success) or
[ @resample = ] 'resample'
sp_updatestats uses the RESAMPLE option of the UPDATE STATISTICS statement. If
resample isn't specified,
sp_updatestats updates statistics by using the default sampling. The
resample argument is varchar(8) with a default value of
UPDATE STATISTICS, by specifying the
ALL keyword, on all user-defined and internal tables in the database.
sp_updatestats displays messages that indicate its progress. When the update is completed, it reports that statistics have been updated for all tables.
sp_updatestats updates statistics on disabled nonclustered indexes and doesn't update statistics on disabled clustered indexes.
For disk-based tables,
sp_updatestats updates statistics based on the
modification_counter information in the sys.dm_db_stats_properties catalog view, updating statistics where at least one row has been modified. Statistics on memory-optimized tables are always updated when executing
sp_updatestats. Therefore don't execute
sp_updatestats more than necessary.
sp_updatestats can trigger a recompile of stored procedures or other compiled code. However,
sp_updatestats might not cause a recompile, if only one query plan is possible for the tables referenced and the indexes on them. A recompilation would be unnecessary in these cases even if statistics are updated.
For databases with a compatibility level below 90, executing
sp_updatestats doesn't preserve the latest NORECOMPUTE setting for specific statistics. For databases with a compatibility level of 90 or higher,
sp_updatestats does preserve the latest NORECOMPUTE option for specific statistics. For more information about disabling and re-enabling statistics updates, see Statistics.
When restoring a database to SQL Server 2022 (16.x) from a previous version, you should execute
sp_updatestats on the database. This is related to setting proper metadata for the statistics auto drop feature introduced in SQL Server 2022 (16.x). The auto drop feature is available in Azure SQL Database, Azure SQL Managed Instance, and starting with SQL Server 2022 (16.x).
For SQL Server, you must be the owner of the database (dbo), or a member of the sysadmin fixed server role.
For Azure SQL Database, you must be a member of the db_owner fixed database role.
The following example updates the statistics for all tables the database:
Automatic index and statistics management
Use solutions such as Adaptive Index Defrag to automatically manage index defragmentation and statistics updates for one or more databases. This procedure automatically chooses whether to rebuild or reorganize an index according to its fragmentation level, among other parameters, and update statistics with a linear threshold.