github/sql-server-samples
1
0
Fork 0
mirror of https://github.com/Microsoft/sql-server-samples.git synced 2025-12-08 14:58:54 +00:00
Code Issues Releases Wiki Activity
Files
d3e5efc059ca8e8c2e0bf0dbe029ace38deb0171
sql-server-samples/samples/manage/sql-assessment-api/DefaultRuleset.csv
T

109 KiB
Raw Blame History

1iditemTypetagsdisplayNamedescriptionmessagehelpLinkprobesconditiontarget.typetarget.platformtarget.engineEditiontarget.versiontarget.name.notcondition.equallevelcondition.incondition.not.intargetFilter.versioncondition.andcondition.notcondition.@HintUsageCountenabledcondition.lesscondition.@ConstraintNamethresholdcondition.not.equalcondition.@page_verify_optioncondition.@filesizeCountcondition.@FileNametarget.namecondition.@Object_Namecondition.@publicationerror_idsseverityNcondition.lecondition.@IsDisabledReadsThresholdcondition.getargetFilter.typetargetFilter.name
20AutoCreateStatsdefinition['DefaultRuleset', 'Performance', 'Statistics', 'QueryOptimizer']Auto-Create Statistics should be onThe Query Optimizer determines whether an index is useful for a specific query by evaluating the stored statistics. If the statistics become out of date and significant changes have occurred against the underlying data, this can result in less than optimal query performance. In most cases, it's best to let SQL Server maintain the statistics. If you turn 'Auto Create Stats' and 'Auto Update Stats' off, then it is up to you to keep the statistics up-to-date somehow. Failure to do so will lead to poor query performance. Most applications should have these options ON. When the Auto Create statistics setting is ON, the Query Optimizer creates statistics on one or more columns of a table or an indexed view, as necessary, to improve query plans and query performance.Turn Auto-Create Statistics option on to improve query performance.https://docs.microsoft.com/sql/relational-databases/statistics/statistics#CreateStatistics['DatabaseConfiguration']@is_auto_create_stats_onDatabase/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Warning
31AutoUpdateStatsdefinition['DefaultRuleset', 'Performance', 'Statistics', 'QueryOptimizer']Auto-Update Statistics should be onThe Query Optimizer determines whether an index is useful for a specific query by evaluating the stored statistics. If the statistics become out of date and significant changes have occurred against the underlying data, this can result in less than optimal query performance. In most cases, it's best to let SQL Server maintain the statistics. If you turn 'Auto Create Stats' and 'Auto Update Stats' off, then it is up to you to keep the statistics up-to-date somehow. Failure to do so will lead to poor query performance. Most applications should have these options ON. When the Auto Update Statistics setting is ON, the Query Optimizer updates statistics when they are used by a query and when they might be out-of-date. Statistics become out-of-date after insert, update, delete, or merge operations change the data distribution in the table or indexed view. The Query Optimizer determines when statistics might be out-of-date by counting the number of data modifications since the last statistics update and comparing the number of modifications to a threshold. The threshold is based on the number of rows in the table or indexed view. The Query Optimizer checks for out-of-date statistics before compiling a query and before executing a cached query plan. Before compiling a query, the Query Optimizer uses the columns, tables, and indexed views in the query predicate to determine which statistics might be out-of-date. Before executing a cached query plan, the Database Engine verifies that the query plan references up-to-date statistics. The AUTO_UPDATE_STATISTICS option applies to statistics created for indexes, single-columns in query predicates, and statistics that are created by using the CREATE STATISTICS statement. This option also applies to filtered statistics.Turn Auto-Update Statistics option on to improve query performance.https://docs.microsoft.com/sql/relational-databases/statistics/statistics#UpdateStatistics['DatabaseConfiguration']@is_auto_update_stats_onDatabase/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Warning
42QueryStoreOndefinition['DefaultRuleset', 'Performance', 'QueryStore', 'Statistics']Query Store should be activeThe Query Store feature provides you with insight on query plan choice and performance. It simplifies performance troubleshooting by helping you quickly find performance differences caused by query plan changes. Query Store automatically captures a history of queries, plans, and runtime statistics, and retains these for your review. It separates data by time windows so you can see database usage patterns and understand when query plan changes happened on the server. While Query Store collects queries, execution plans and statistics, its size in the database grows until this limit is reached. When that happens, Query Store automatically changes the operation mode to read-only and stops collecting new data, which means that your performance analysis is no longer accurate.Make sure Query Store actual operation mode is 'Read Write' to keep your performance analysis accuratehttps://docs.microsoft.com/sql/relational-databases/performance/monitoring-performance-by-using-the-query-store['DatabaseConfiguration']Database/^(Windows|Linux)$/OnPremises, ManagedInstance[13.0,)/^(master|tempdb|model)$/['@query_store_state', 2]Warning
53TF174definition['DefaultRuleset', 'TraceFlag', 'Memory', 'Performance']TF 174 increases the plan cache bucket countTrace Flag 174 increases the SQL Server plan cache bucket count from 40,009 to 160,001 on 64-bit systems. When the SQL Server plan cache reaches its entry limit, plans that have low cost must be evicted in order to insert new plans. This can cause severe contention on the SOS_CACHESTORE spinlock and a high CPU usage occurs in SQL Server. On 64-bit systems, the number of buckets for the SQL Server plan cache is 40,009. Therefore, the maximum number of entries that can fit inside the SQL Server plan cache is 160,036. Enabling trace flag 174 on high performance systems increases the size of the cache and can avoid SOS_CACHESTORE spinlock contention.Consider enabling trace flag 174 to increase the plan cache bucket count.https://docs.microsoft.com/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql['EnabledGlobalTraceFlags']Server/^(Windows|Linux)$/OnPremises['[11.0.3368,12.0)', '[12.0.2480,13.0)', '[13.0,)']Information[174, '@TraceFlag']
64TF634definition['DefaultRuleset', 'TraceFlag', 'Memory', 'Performance', 'ColumnStore']TF 634 disables background columnstore compressionTrace Flag 634 disables the background columnstore compression task. SQL Server periodically runs the Tuple Mover background task that compresses columnstore index rowgroups with uncompressed data, one such rowgroup at a time. Columnstore compression improves query performance but also consumes system resources. You can control the timing of columnstore compression manually, by disabling the background compression task with trace flag 634, and then explicitly invoking ALTER INDEX...REORGANIZE or ALTER INDEX...REBUILD at the time of your choice.Trace Flag 634 disables the background columnstore compression task. Verify need to set a non-default trace flag with the current system build and configuration.https://docs.microsoft.com/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql['EnabledGlobalTraceFlags']Server/^(Windows|Linux)$/OnPremises[11.0,)Information[634, '@TraceFlag']
75TF652definition['DefaultRuleset', 'TraceFlag', 'Performance', 'Memory', 'Pages']TF 652 disables page pre-fetching scansTrace Flag 652 disables page pre-fetching for scans. The read-ahead process reads the full extent of a referenced database page into the buffer pool, before those contiguous database pages are consumed by scans. Enabling the trace flag can lead to performance issues on queries that leverage pre-fetching.Trace Flag 652 disables Page Pre-fetching Scans. Verify need to set a non-default trace flag with the current system build and configuration.http://support.microsoft.com/kb/920093['EnabledGlobalTraceFlags']ServerWindowsOnPremises[11.0,)Information[652, '@TraceFlag']
86TF661definition['DefaultRuleset', 'TraceFlag', 'Performance']TF 661 disables Ghost Cleanup TaskTrace Flag 661 disables the ghost record removal process. A ghost record is the result of a delete operation. When you delete a record, the deleted record is kept as a ghost record. Later, the deleted record is purged by the ghost record removal process. When you disable this process, the deleted record is not purged. Therefore, the space that the deleted record consumes is not freed. This behavior affects space consumption and the performance of scan operations. If you turn off this trace Flag, the ghost record removal process works correctly.Trace flag 661 disables the background ghost cleanup task. Verify need to set a non-default trace flag with the current system build and configuration.https://support.microsoft.com/help/920093['EnabledGlobalTraceFlags']ServerWindowsOnPremises[11.0,)Information[661, '@TraceFlag']
97TF834definition['DefaultRuleset', 'TraceFlag', 'Performance', 'Memory', 'ColumnStore']TF 834 enables large-page allocationsTrace Flag 834 causes the server to use large-page memory (LPM) model for the buffer pool allocations. Consider enabling TF 834 if you have a server that has a lot of memory, particularly for an analytical or data warehousing workload. Trace flag 834 is NOT recommended on SQL Server instances that use columnstore indexes.Enable trace flag 834 to use large-page allocations to improve analytical and data warehousing workloads.https://support.microsoft.com/help/4465518['EnabledGlobalTraceFlags']Server/^(Windows|Linux)$/OnPremises[11.0,)Information[834, '@TraceFlag']
108TF845definition['DefaultRuleset', 'TraceFlag', 'Memory', 'Performance']TF 845 is not needed in SQL Server 2012 and higher versionsTrace Flag 845 supports locking pages in memory in SQL Server Standard edition, which is needed together with trace flag 834 to use the large-page memory (LPM) model for the buffer pool allocations. Consider enabling TF 834 if you have a server that has a lot of memory, particularly for an analytical or data warehousing workload. Starting with SQL Server 2012 this behavior is enabled by default for Standard edition, and trace flag 845 must not be used.Disable trace flag 845 in SQL Server 2012 and higher versions.https://docs.microsoft.com/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql['EnabledGlobalTraceFlags']ServerWindowsOnPremises[11.0,)Warning[845, '@TraceFlag']
119TF902definition['DefaultRuleset', 'TraceFlag', 'UpdateIssues']TF 902: Database Upgrade Bypass should be disabledTrace Flag 902 bypasses execution of database upgrade script when installing a Cumulative Update or Service Pack. This trace flag is not supported to run it continuously in a production environment. If you encounter an error during script upgrade mode, it is recommended to contact Microsoft SQL Customer Service and Support (CSS) for further guidance.Disable trace flag 902 which bypasses database upgrade.https://support.microsoft.com/help/2163980['EnabledGlobalTraceFlags']ServerWindowsOnPremises[11.0,)Warning[902, '@TraceFlag']
1210TF1117definition['DefaultRuleset', 'TraceFlag', 'DBFileConfiguration', 'Performance']TF 1117 Enables Filegroup-level AutogrowTrace Flag 1117 initiates the growth of every file in the filegroup, when a file in the filegroup meets the autogrow threshold, and together with trace flag 1118, can help reduce allocation contention in the SQL Server TempDB database. This trace flag affects all databases and is recommended only if every database is safe to be grow all files in a filegroup by the same amount.Consider enabling trace flag 1117 to enable filegroup autogrow.https://support.microsoft.com/help/2154845['EnabledGlobalTraceFlags']ServerWindowsOnPremises[11.0,)Information[1117, '@TraceFlag']
1311TF1117overrideTF 1117 has no effect in SQL Server 2016 and higher versionsTrace Flag 1117 initiates the growth of every file in the filegroup, when a file in the filegroup meets the autogrow threshold, and together with trace flag 1118, can help reduce allocation contention in the SQL Server TempDB database. Starting with SQL Server 2016, this behavior is controlled by the AUTOGROW_SINGLE_FILE and AUTOGROW_ALL_FILES options of ALTER DATABASE syntax.Disable trace flag 1117 in SQL Server 2016 and higher versions.https://docs.microsoft.com/sql/t-sql/statements/alter-database-transact-sql-file-and-filegroup-optionsWarning[1117, '@TraceFlag'][13.0,)
1412TF1118definition['DefaultRuleset', 'TraceFlag', 'Memory', 'Performance', 'Pages']TF 1118 Disables Single Page AllocationsTrace Flag 1118 forces page allocations on uniform extents instead of mixed extents, and together with trace flag 1117, can help reduce allocation contention in the SQL Server TempDB database. When a new object is created, by default, the first eight pages are allocated from different extents (mixed extents). Afterwards, when more pages are needed, those are allocated from that same extent (uniform extent). The SGAM page is used to track these mixed extents, so can quickly become a bottleneck when numerous mixed page allocations are occurring. This trace flag allocates all eight pages from the same extent when creating new objects, minimizing the need to scan the SGAM page and forces uniform extent allocations instead of mixed page allocations.Consider enabling trace flag 1118 to force page allocations on uniform extents.https://support.microsoft.com/help/328551['EnabledGlobalTraceFlags']ServerWindowsOnPremises[11.0,)Information[1118, '@TraceFlag']
1513TF1118overrideTF 1118 has no effect in SQL Server 2016 and higher versionsTrace Flag 1118 forces page allocations on uniform extents instead of mixed extents, and together with trace flag 1117, can help reduce allocation contention in the SQL Server TempDB database. When a new object is created, by default, the first eight pages are allocated from different extents (mixed extents). Afterwards, when more pages are needed, those are allocated from that same extent (uniform extent). The SGAM page is used to track these mixed extents, so can quickly become a bottleneck when numerous mixed page allocations are occurring. This trace flag allocates all eight pages from the same extent when creating new objects, minimizing the need to scan the SGAM page and forces uniform extent allocations instead of mixed page allocations. Starting with SQL Server 2016, this behavior is controlled by the SET MIXED_PAGE_ALLOCATION option of ALTER DATABASE syntax.Disable trace flag 1118 in SQL Server 2016 and higher versions.https://docs.microsoft.com/sql/t-sql/statements/alter-database-transact-sql-file-and-filegroup-optionsWarning[1118, '@TraceFlag'][13.0,)
1614TF1204definition['DefaultRuleset', 'TraceFlag', 'Locks', 'Performance']TF 1204 returns deadlock informationTrace Flag 1204 returns the resources and types of locks that are participating in a deadlock, including the affected command. The resulting information is recorded in the SQL Server Errorlog.Trace Flag 1204 returns deadlock information.https://support.microsoft.com/help/832524['EnabledGlobalTraceFlags']Server/^(Windows|Linux)$/OnPremises[11.0,)Information[1204, '@TraceFlag']
1715TF1211definition['DefaultRuleset', 'TraceFlag', 'Locks', 'Performance']TF 1211: Lock Escalation should be enabledTrace Flag 1211 disables lock escalation based on memory pressure, or based on number of locks. Because SQL Server will not escalate row or page locks to table locks, this can generate an excessive number of locks. If the lock memory grows large enough, attempts to allocate additional locks for any query may fail and cause performance issues. This trace flag should not be used in order to avoid inability to allocate lock resources because of insufficient memory. If lock escalation needs to be disabled, use trace flag 1224 instead.Disable trace flag 1211 to allow lock escalation.https://docs.microsoft.com/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql['EnabledGlobalTraceFlags']Server/^(Windows|Linux)$/OnPremises[11.0,)Warning[1211, '@TraceFlag']
1816TF1222definition['DefaultRuleset', 'TraceFlag', 'Locks', 'Performance']TF 1222 returns deadlock informationTrace Flag 1222 returns the resources and types of locks that are participating in a deadlock, including the affected command. The resulting information is recorded in the SQL Server Errorlog, in XML format that does not comply with any XSD schema.Trace Flag 1222 returns deadlock information.https://docs.microsoft.com/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql['EnabledGlobalTraceFlags']Server/^(Windows|Linux)$/OnPremises[11.0,)Information[1222, '@TraceFlag']
1917TF1224definition['DefaultRuleset', 'TraceFlag', 'Locks', 'Performance']TF 1224 should be disabledTrace Flag 1224 disables lock escalation based on the number of locks, unless SQL Server is under memory pressure. Because SQL Server will not escalate row or page locks to table locks, this can generate an excessive number of locks.Disable trace flag 1224 to allow lock escalation.https://docs.microsoft.com/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql['EnabledGlobalTraceFlags']Server/^(Windows|Linux)$/OnPremises[11.0,)Warning[1224, '@TraceFlag']
2018TF1229definition['DefaultRuleset', 'TraceFlag', 'Locks', 'Performance', 'CPU']TF 1229: Lock Partitioning should be enabledTrace Flag 1229 disables lock partitioning regardless of the number of CPUs. By default, SQL Server enables lock partitioning when a server has 16 or more CPUs, to improve the scalability characteristics of larger systems. Disabling lock partitioning may cause can cause spinlock contention and poor performance, or unexpected behaviors when switching partitions.Disable trace flag 1229 to allow lock partitioning.https://docs.microsoft.com/sql/relational-databases/sql-server-transaction-locking-and-row-versioning-guide['EnabledGlobalTraceFlags']Server/^(Windows|Linux)$/OnPremises[11.0,)Warning[1229, '@TraceFlag']
2119TF1236definition['DefaultRuleset', 'TraceFlag', 'Locks', 'Performance']TF 1236: Database Lock Partitioning should be enabledTrace Flag 1236 enables database-level lock partitioning. Lock Partitioning is utilized to improve the scalability characteristics on larger systems.Enable trace Flag 1236 to allow database lock partitioning.https://support.microsoft.com/help/2926217['EnabledGlobalTraceFlags']ServerWindowsOnPremises[11.0,)Warning[1236, '@TraceFlag']
2220TF1236overrideTF 1236 is not needed in SQL Server 2012 SP3, SQL Server 2014 SP1 and higher versionsTrace Flag 1236 enables database-level lock partitioning. Starting with SQL Server 2012 SP3 and SQL Server 2014 SP1, this behavior is controlled by the engine and trace flag 1236 has no effect.Disable trace flag 1236 in SQL Server 2012 SP3, SQL Server 2014 SP1 and higher versions.Warning[1236, '@TraceFlag']['[11.0.6020,12.0)', '[12.0.4100,)']
2321TF1462definition['DefaultRuleset', 'TraceFlag', 'Performance', 'AvailabilityGroups']TF 1462 should be disabled to allow Log Stream CompressionTrace Flag 1462 disables log stream compression for asynchronous availability groups. This feature is enabled by default on asynchronous replicas to optimize network bandwidth.Disable trace flag 1462 to allow log stream compression.https://docs.microsoft.com/sql/database-engine/availability-groups/windows/tune-compression-for-availability-group['EnabledGlobalTraceFlags']Server/^(Windows|Linux)$/OnPremises[11.0,)Warning[1462, '@TraceFlag']
2422TF2312definition['DefaultRuleset', 'TraceFlag', 'QueryOptimizer', 'Performance']TF 2312 sets the default Cardinality Estimation modelTrace Flag 2312 sets the Query Optimizer cardinality estimation model to the default version of the database compability level of SQL Server 2014 and higher versions. If the database compatibility level is lower than 120, enabling trace flag 2312 uses the cardinality estimation model of SQL Server 2014 (120).Trace Flag 2312 does not apply to this SQL Server version. Verify need to set a non-default trace flag with the current system build and configuration.https://support.microsoft.com/help/2801413['EnabledGlobalTraceFlags']ServerWindowsOnPremises[11.0,)Warning[2312, '@TraceFlag']
2523TF2312override['DefaultRuleset', 'TraceFlag', 'QueryOptimizer', 'Performance']Information[12.0, 13.0)
2624TF2312override['DefaultRuleset', 'TraceFlag', 'QueryOptimizer', 'Performance']TF2312 enables New CE model to SQL Server 2014 or above versions, dependent of the compatibility level of the databaseInformation[13.0, )
2725TF2330definition['DefaultRuleset', 'TraceFlag', 'Performance', 'Indexes']TF 2330 disables recording of index usage statsTrace Flag 2330 disables recording of index usage stats, which could lead to a non-yielding condition in SQL 2005.Trace Flag 2330 does not apply to this SQL Server version. Verify need to set a non-default trace flag with the current system build and configuration.https://blogs.msdn.microsoft.com/ialonso/2012/10/08/faq-around-sys-dm_db_index_usage_stats['EnabledGlobalTraceFlags']Server/^(Windows|Linux)$/OnPremises[11.0,)Warning[2330, '@TraceFlag']
2826TF2340definition['DefaultRuleset', 'TraceFlag', 'QueryOptimizer', 'Performance']TF 2340 disables Batch Sorts for optimized nested loops joinsTrace Flag 2340 causes SQL Server not to use a sort operation (batch sort) for optimized nested loops joins when generating a plan. Verify need to set a non-default trace flag with the current system build and configuration.Trace Flag 2340 disables Batch Sorts for optimized nested loops joins.https://docs.microsoft.com/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql['EnabledGlobalTraceFlags']Server/^(Windows|Linux)$/OnPremises[11.0,)Information[2340, '@TraceFlag']
2927TF2371definition['DefaultRuleset', 'TraceFlag', 'Performance', 'Statistics']TF 2371 enables a linear recompilation threshold for statisticsTrace Flag 2371 causes SQL Server to change the fixed update statistics threshold to a linear update statistics threshold. This is especially useful to keep statistics updated on large tables.Enable trace Flag 2371 to allow a linear recompilation threshold for statistics.https://docs.microsoft.com/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql['EnabledGlobalTraceFlags']ServerWindowsOnPremises[11.0,)Information[2371, '@TraceFlag']
3028TF2371overrideTF 2371 has no effect in SQL Server 2016 and higher versionsTrace Flag 2371 causes SQL Server to change the fixed update statistics threshold to a linear update statistics threshold. This is especially useful to keep statistics updated on large tables. Starting with SQL Server 2016, for databases using compatibility level 130 and above, this behavior is controlled by the engine and trace flag 2371 has no effect.Disable trace flag 2371 in SQL Server 2016 and higher versions when all databases are at compatibility level 130 and above.Warning[2371, '@TraceFlag'][13.0,)
3129TF2389definition['DefaultRuleset', 'TraceFlag', 'Statistics', 'Performance']TF 2389 enables automatic statistics for Ascending KeysTrace Flag 2389 enables automatically generated quick statistics for ascending keys (histogram amendment). This trace flag is recommended to be set in cases where queries access newly inserted ascending key values (such as an IDENTITY column), but the new values are not yet updated in the statistics histogram for the affected columns. In this case the histogram used to estimate cardinality will be adjusted at query compile time. Verify need to set a non-default trace flag with the current system build and configuration.Trace Flag 2389 enables automatic statistics for ascending keys. Verify need to set a non-default trace flag with the current system build and configuration.https://support.microsoft.com/help/2801413['EnabledGlobalTraceFlags']Server/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Information[2389, '@TraceFlag']
3230TF2390definition['DefaultRuleset', 'TraceFlag', 'Statistics', 'Performance', 'Indexes']TF 2390 enables automatic statistics for Ascending or Unknown KeysTrace Flag 2390 enables automatically generated quick statistics for ascending or unknown keys (histogram amendment). This trace flag is recommended to be set in cases where queries access newly inserted ascending key values (such as an IDENTITY column), but the new values are not yet updated in the statistics histogram for the affected columns. In this case the histogram used to estimate cardinality will be adjusted at query compile time. Verify need to set a non-default trace flag with the current system build and configuration.Trace Flag 2390 enables automatic statistics for ascending or unknown keys. Verify need to set a non-default trace flag with the current system build and configuration.https://support.microsoft.com/help/2801413['EnabledGlobalTraceFlags']Server/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Information[2390, '@TraceFlag']
3331TF2528definition['DefaultRuleset', 'TraceFlag', 'DataIntegrity', 'DBCC']TF 2528 disables parallel operations for integrity checkingTrace Flag 2528 disables parallel checking of objects by DBCC CHECKDB, DBCC CHECKFILEGROUP, and DBCC CHECKTABLE. By default, the degree of parallelism is automatically determined by the query processor. The maximum degree of parallelism is configured just like that of parallel queries. When parallel checks are disabled, the DBCC commands will take longer to complete. Starting with SQL Server 2014 SP2, a MAXDOP option is available to override the max degree of parallelism configuration option of sp_configure for the DBCC statements.Trace Flag 2528 disables parallel operations for integrity checking.https://docs.microsoft.com/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql['EnabledGlobalTraceFlags']Server/^(Windows|Linux)$/OnPremises[11.0,)Warning[2528, '@TraceFlag']
3432TF2549definition['DefaultRuleset', 'TraceFlag', 'DBCC']TF 2549 optimizes PHYSICAL_ONLY option of DBCC CHECKDBTrace Flag 2549 forces the DBCC CHECKDB command to assume each database file is on a unique disk drive but treating different physical files as one logical file. This trace flag can improve the performance when using the PHYSICAL_ONLY option, but it's not recommended unless it is known that each file is based on a unique physical disk.Trace Flag 2549 forces DBCC CHECKDB to treat different physical files as one logical file.https://support.microsoft.com/help/2634571['EnabledGlobalTraceFlags']Server/^(Windows|Linux)$/OnPremises[11.0,)Warning[2549, '@TraceFlag']
3533TF2562definition['DefaultRuleset', 'TraceFlag', 'DBCC', 'TempDB']TF 2562 forces the DBCC CHECKDB command to execute in a single batchTrace Flag 2562 forces the DBCC CHECKDB command to execute in a single batch regardless of the number of indexes in the database. This trace flag can improve the performance when using the PHYSICAL_ONLY option, but space requirements for TempDB may increase.Trace Flag 2562 forces the DBCC CHECKDB command to execute in a single batch.https://support.microsoft.com/help/2634571['EnabledGlobalTraceFlags']Server/^(Windows|Linux)$/OnPremises[11.0,)Warning[2562, '@TraceFlag']
3634TF2566definition['DefaultRuleset', 'TraceFlag', 'DBCC', 'DataIntegrity']TF 2566 disables default data purity checkTrace Flag 2566 forces the DBCC CHECKDB command to execute without data purity check unless the DATA_PURITY option is specified. For databases upgraded from earlier versions of SQL Server, it is recommended to run the DBCC CHECKDB WITH DATA_PURITY command at least once, to enable column-value integrity checks to happen by default.Trace Flag 2566 disables default data purity check.https://support.microsoft.com/help/945770['EnabledGlobalTraceFlags']Server/^(Windows|Linux)$/OnPremises[11.0,)Warning[2566, '@TraceFlag']
3735TF3023definition['DefaultRuleset', 'TraceFlag', 'Backup']TF 3023 enables Backup Checksum option by defaultTrace Flag 3023 enables the CHECKSUM option of the BACKUP command by default. This trace flag forces the CHECKSUM option for BACKUP command even when not explicitely set. Starting with SQL Server 2014, this behavior is controlled by setting the Backup Checksum Default configuration option.Trace Flag 3023 enables CHECKSUM option as default for BACKUP command.https://support.microsoft.com/help/2656988['EnabledGlobalTraceFlags']ServerWindowsOnPremises[11.0,)Information[3023, '@TraceFlag']
3836TF3042definition['DefaultRuleset', 'TraceFlag', 'Backup']TF 3042 bypasses the default backup compression pre-allocation algorithmTrace Flag 3042 bypasses the default backup compression pre-allocation algorithm to allow the backup file to grow only as needed to reach its final size. This trace flag can achieve space savings by allocating only the actual size required for the compressed backup, but might increase the overall backup operation time.Trace Flag 3042 enables the bypass of the default backup compression.https://docs.microsoft.com/sql/relational-databases/backup-restore/backup-compression-sql-server['EnabledGlobalTraceFlags']Server/^(Windows|Linux)$/OnPremises[11.0,)Information[3042, '@TraceFlag']
3937TF3226definition['DefaultRuleset', 'TraceFlag', 'Backup']TF 3226 disables ErrorLog entries for every successful backup operationTrace Flag 3226 prevents SQL Server from recording an entry to the Errorlog on every successful backup operation. Backup operations are registered in the Errorlog by default. Frequent backup operations can contribute to massive Errorlog files that become unwieldy.Trace Flag 3226 disables ErrorLog entries for every successful backup operation.https://docs.microsoft.com/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql['EnabledGlobalTraceFlags']Server/^(Windows|Linux)$/OnPremises[11.0,)Information[3226, '@TraceFlag']
4038TF4136overrideTrace Flag 4136 disables parameter sniffing unless OPTION(RECOMPILE), WITH RECOMPILE or OPTIMIZE FOR value is used. Starting with SQL Server 2016, to accomplish this at the database level use the PARAMETER_SNIFFING option in ALTER DATABASE SCOPED CONFIGURATION. Verify need to set a non-default trace flag with the current system build and configuration.Trace Flag 4136 disables parameter sniffing. Verify need to set a non-default trace flag with the current system build and configuration.Information[11.0.2316,)
4139TF4136definition['DefaultRuleset', 'TraceFlag']TF 4136 disables Parameter SniffingTrace Flag 4136 disables parameter sniffing unless OPTION(RECOMPILE), WITH RECOMPILE or OPTIMIZE FOR value is used, but does not apply to this SQL Server version. Starting with SQL Server 2016, to accomplish this at the database level use the PARAMETER_SNIFFING option in ALTER DATABASE SCOPED CONFIGURATION. Verify need to set a non-default trace flag with the current system build and configuration.Trace Flag 4136 does not apply to this SQL Server version. Verify need to set a non-default trace flag with the current system build and configuration.https://support.microsoft.com/help/980653['EnabledGlobalTraceFlags']Server/^(Windows|Linux)$/OnPremises[11.0,)Warning[4136, '@TraceFlag']
4240TF4137overrideTrace Flag 4137 causes SQL Server to generate a plan using minimum selectivity when estimating AND predicates for filters to account for partial correlation instead of independence, under the query optimizer cardinality estimation model of SQL Server 2012 and earlier versions (CE 70). Does not apply to CE version 120 or above. Use trace flag 9471 instead. Starting with SQL Server 2016 SP1, to accomplish this at the query level use the USE HINT 'ASSUME_MIN_SELECTIVITY_FOR_FILTER_ESTIMATES' query hint. Verify need to set a non-default trace flag with the current system build and configuration.Trace Flag 4137 causes SQL Server to generate a plan using partial correlation of filters. Verify need to set a non-default trace flag with the current system build and configuration.Information[11.0.2316,)
4341TF4137definition['DefaultRuleset', 'TraceFlag', 'QueryOptimizer', 'Performance']TF 4137 causes plans to use partial correlation for filtersTrace Flag 4137 causes SQL Server to generate a plan using minimum selectivity when estimating AND predicates for filters to account for partial correlation instead of independence, under the query optimizer cardinality estimation model of SQL Server 2012 and earlier versions (CE 70). However it does not apply to this SQL Server version. Does not apply to CE version 120 or above. Use trace flag 9471 instead. Starting with SQL Server 2016 SP1, to accomplish this at the query level use the USE HINT 'ASSUME_MIN_SELECTIVITY_FOR_FILTER_ESTIMATES' query hint. Verify need to set a non-default trace flag with the current system build and configuration.Trace flag 4137 does not apply to this SQL Server version. Verify need to set a non-default trace flag with the current system build and configuration.https://support.microsoft.com/help/2658214['EnabledGlobalTraceFlags']Server/^(Windows|Linux)$/OnPremises[11.0,)Warning[4137, '@TraceFlag']
4442TF4138overrideTrace Flag 4138 causes SQL Server to generate a plan that does not use row goal adjustments with queries that contain TOP, OPTION (FAST N), IN, or EXISTS keywords. Starting with SQL Server 2016 SP1, to accomplish this at the query level use the USE HINT 'DISABLE_OPTIMIZER_ROWGOAL' query hint. Verify need to set a Non-default trace flag with current system build and configuration.Trace Flag 4138 enables plan that without row goal adjustments. Verify need to set a non-default trace flag with the current system build and configuration.Information[11.0.2325,)
4543TF4138definition['DefaultRuleset', 'TraceFlag', 'QueryOptimizer', 'Performance']TF 4138 causes plans to not use Row Goal adjustmentsTrace Flag 4138 causes SQL Server to generate a plan that does not use row goal adjustments with queries that contain TOP, OPTION (FAST N), IN, or EXISTS keywords. Starting with SQL Server 2016 SP1, to accomplish this at the query level use the USE HINT 'DISABLE_OPTIMIZER_ROWGOAL' query hint. However it does not apply to this SQL Server version. Verify need to set a Non-default trace flag with current system build and configuration.Trace flag 4138 does not apply to this SQL Server version. Verify need to set a non-default trace flag with the current system build and configuration.https://support.microsoft.com/help/2667211['EnabledGlobalTraceFlags']Server/^(Windows|Linux)$/OnPremises[11.0,)Warning[4138, '@TraceFlag']
4644TF4139overrideTrace Flag 4139 enables automatically generated quick statistics (histogram amendment) regardless of key column status. This trace flag is recommended to be set in cases where queries access newly inserted key values that may change plan shape, but the new values are not yet updated in the statistics histogram for the affected columns. In this case, regardless of the leading statistics column status (ascending, descending, or stationary), the histogram used to estimate cardinality will be adjusted at query compile time. This trace flag does not apply to the cardinality estimation model of SQL Server 2012 and earlier versions (CE 70). Verify need to set a non-default trace flag with the current system build and configuration.Trace Flag 4139 enables automatic statistics for any key ordering. Verify need to set a non-default trace flag with the current system build and configuration.Information['[11.0.3431,11.0.5058)', '[11.0.5532,)']
4745TF4139definition['DefaultRuleset', 'TraceFlag', 'Statistics']TF 4139 enables automatic statistics for any key orderingTrace Flag 4139 enables automatically generated quick statistics (histogram amendment) regardless of key column status. However, this trace flag does not apply to this SQL Server version. Verify need to set a non-default trace flag with the current system build and configuration.Trace flag 4139 does not apply to this SQL Server version. Verify need to set a non-default trace flag with the current system build and configuration.https://support.microsoft.com/help/2952101['EnabledGlobalTraceFlags']Server/^(Windows|Linux)$/OnPremises[11.0,)Warning[4139, '@TraceFlag']
4846TF4199definition['DefaultRuleset', 'TraceFlag', 'QueryOptimizer']TF 4199 enables Query Optimizer fixesTrace Flag 4199 enables Query Optimizer fixes released in SQL Server Cumulative Updates and Service Packs.Trace Flag 4199 enables Query Optimizer fixes. Verify need to set a non-default trace flag with the current system build and configuration.http://support.microsoft.com/help/974006['EnabledGlobalTraceFlags']Server/^(Windows|Linux)$/OnPremises[11.0, 14.0)Information[4199, '@TraceFlag']
4947TF6498overrideTrace Flag 6498 enables concurrent large queries.Information['[12.0.2474,12.0.2480]', '[12.0.4416,12.0.5000)']
5048TF6498overrideTrace Flag 6498 enables more than one large query compilation to gain access to the big gateway when there is sufficient memory available. This trace flag can be used to keep memory usage for the compilation of incoming queries under control, avoiding compilation waits for concurrent large queries. Starting with SQL Server 2014 SP2 and SQL Server 2016, this behavior is controlled by the engine and trace flag 1236 has no effect.Disable trace flag 6498 in SQL Server 2014 SP2, SQL Server 2016 and higher versions.Warning[12.0.5000,)
5149TF6498definition['DefaultRuleset', 'TraceFlag', 'Performance', 'Memory']TF 6498 enables additional concurrent large queriesTrace Flag 6498 enables more than one large query compilation to gain access to the big gateway when there is sufficient memory available. However, this trace flag does not apply to this SQL Server version. This trace flag can be used to keep memory usage for the compilation of incoming queries under control, avoiding compilation waits for concurrent large queries. Starting with SQL Server 2014 SP2 and SQL Server 2016, this behavior is controlled by the engine and trace flag 1236 has no effect.Trace Flag 6498 does not apply to this SQL Server version. Verify need to set a non-default trace flag with the current system build and configuration.https://support.microsoft.com/help/3024815['EnabledGlobalTraceFlags']ServerWindowsOnPremises[11.0,)Warning[6498, '@TraceFlag']
5250TF6532definition['DefaultRuleset', 'TraceFlag', 'Performance']TF 6532 enables performance improvements for Spatial dataTrace Flag 6532 enables performance improvements of query operations with spatial data types. The performance gain will vary, depending on the configuration, the types of queries, and the objects.Enable trace flag 6532 to enable performance improvements for Spatial data.https://support.microsoft.com/help/3107399['EnabledGlobalTraceFlags']ServerWindowsOnPremises['[11.0.6020,11.0.6518)']Information[6532, '@TraceFlag']
5351TF6532.6533overrideTrace Flag 6532 and trace flag 6533 enable performance improvements of query operations with spatial data types. The performance gain will vary, depending on the configuration, the types of queries, and the objects.Enable trace flag 6532 and trace flag 6533 to enable performance improvements for Spatial data.Information['[11.0.6518,12.0)', '[12.0.5000,13.0)'][{'in': [6532, '@TraceFlag']}, {'in': [6533, '@TraceFlag']}]
5452TF6532.6533overrideDisable trace flag 6532 in SQL Server 2016 and higher versions.Warning[13.0,)
5553TF6532.6533definition['DefaultRuleset', 'TraceFlag', 'Performance']TF 6532 and TF 6533 enable performance improvements for Spatial dataTrace flags 6532 and 6533 enable performance improvements of query operations with spatial data types. However, this trace flag does not apply to this SQL Server version. Starting with SQL Server 2016, this behavior is controlled by the engine and trace flags 6532 and 6533 have no effect.Trace flags 6532 and 6533 do not apply to this SQL Server version. Verify need to set a non-default trace flag with the current system build and configuration.https://support.microsoft.com/help/3107399['EnabledGlobalTraceFlags']ServerWindowsOnPremises[11.0,)Warning[{'not': {'in': [6532, '@TraceFlag']}}, {'not': {'in': [6533, '@TraceFlag']}}]
5654TF6534overrideTrace Flag 6534 enables performance improvements of query operations with spatial data types. The performance gain will vary, depending on the configuration, the types of queries, and the objects.Enable trace flag 6534 to enable performance improvement of query operations with spatial data types.Information[6534, '@TraceFlag']['[11.0.6020,12.0)', '[12.0.5000,13.0)']
5755TF6534definition['DefaultRuleset', 'TraceFlag', 'Performance']TF 6534 enables performance improvements for Spatial dataTrace Flag 6534 enables performance improvement of query operations with spatial data types. However, this trace flag does not apply to this SQL Server version. Verify need to set a Non-default trace flag with current system build and configuration.Trace flag 6534 does not apply to this SQL Server version. Verify need to set a non-default trace flag with the current system build and configuration.https://support.microsoft.com/help/3107399['EnabledGlobalTraceFlags']ServerWindowsOnPremises[11.0,)Warning[6534, '@TraceFlag']
5856TF7412definition['DefaultRuleset', 'TraceFlag', 'Performance']TF 7412 enables the lightweight profiling infrastructure for live query performance troubleshootingTrace Flag 7412 enables the lightweight profiling infrastructure for live query performance troubleshooting. Consider enabling TF 7412 to have the ability to access runtime information on query execution plans for any session.Enable trace flag 7412 to enables the lightweight profiling infrastructure for live query performance troubleshooting.https://docs.microsoft.com/sql/relational-databases/performance/query-profiling-infrastructure['EnabledGlobalTraceFlags']Server/^(Windows|Linux)$/OnPremises[13.0.4001,15.0)Information[7412, '@TraceFlag']
5957TF9024definition['DefaultRuleset', 'TraceFlag', 'Performance', 'NUMA', 'Memory', 'CPU']TF 9024 converts a global log pool memory object into NUMA node partitioned memory objectTF9024 converts a global log pool memory object into NUMA node partitioned memory object.Verify need to set a Non-default TF with current system build and configuration.https://support.microsoft.com/help/2809338/fix-high-log-write-waits-counter-value-on-a-sql-server-2012-or-sql-ser['EnabledGlobalTraceFlags']ServerWindowsOnPremisesWarning[9024, '@TraceFlag']
6058TF9024overrideConsider enabling TF9024 to convert global log pool memory objects into NUMA node partitioned memory objects.['EnabledGlobalTraceFlags', 'ServerInstanceConfiguration'][{'in': [9024, '@TraceFlag']}, {'gt': [8, {'div': ['@online_logical_processors', '@numa_nodes']}]}]Information['[11.0.3349, 11.0.6020)', '[12.0, 12.0.4100)']
6159TF9024overrideTF9024 is not needed in SQL Server 2012 SP3, SQL Server 2014 SP1 and above.Warning['[11.0.6020, 12.0)', '[12.0.4100,)']
6260TF8048definition['DefaultRuleset', 'TraceFlag', 'Performance', 'NUMA', 'CPU', 'Memory']TF 8048 converts NUMA partitioned memory objects into CPU partitionedTF 8048 converts NUMA partitioned memory objects into CPU partitioned.Verify need to set a Non-default TF with current system build and configuration.https://support.microsoft.com/help/2809338/fix-high-log-write-waits-counter-value-on-a-sql-server-2012-or-sql-ser['EnabledGlobalTraceFlags']ServerWindowsOnPremisesWarning[8048, '@TraceFlag']
6361TF8048overrideTF8048 is not needed in SQL Server 2014 SP2, SQL Server 2016 and above.Warning[12.0.4100,)
6462TF8048overrideConsider enabling TF 8048 to convert NUMA partitioned memory objects into CPU partitioned.['EnabledGlobalTraceFlags', 'ServerInstanceConfiguration'][{'in': [8048, '@TraceFlag']}, {'gt': [8, {'div': ['@online_logical_processors', '@numa_nodes']}]}]Information[11.0, 12.0.4100)
6563DeprecatedFeaturesdefinition['DefaultRuleset', 'Deprecated', 'Security', 'UpdateIssues', 'Performance']Deprecated or discontinued features should not be usedThis check detects deprecated or discontinued features used on target SQL Server instance. Deprecated features may be removed in a future release of SQL Server. Discontinued features have been removed from specific versions of SQL Server.Detected deprecated or discontinued feature uses: @{DeprecatedFeature}. We recommend to replace them with features actual for SQL Server version @{ProductVersion}.https://docs.microsoft.com/sql/relational-databases/performance-monitor/sql-server-deprecated-features-object['DeprecatedFeaturesStats', 'SQLServerVersion']Server/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)/^(master|tempdb|model|msdb)$/['@DeprecatedFeature', '']Warning
6664SystemHealthSessiondefinition['DefaultRuleset', 'XEvent', 'SystemHealth']system_health XEvent session is not activeThis session starts automatically when the SQL Server Database Engine starts, and runs without any noticeable performance effects. The session collects system data that you can use to help troubleshoot performance issues in the Database Engine. We recommend that you do not stop, alter, or delete the system health session.Start the session by using the ALTER EVENT SESSION statement or by using the Extended Events node in Object Explorer.https://docs.microsoft.com/sql/relational-databases/extended-events/use-the-system-health-session['XEvent.SystemHealth']@XEvent.SystemHealthCountServer/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Warning
6765SPServerDiagnosticsSessiondefinition['DefaultRuleset', 'XEvent', 'SystemHealth']sp_server_diagnostics xEvent session is not activeThis session starts automatically when the SQL Server Database Engine starts, and runs without any noticeable performance effects. The session collects system data that you can use to help troubleshoot performance issues in the Database Engine. We recommend that you do not stop, alter, or delete the system health session.Start the session by using the ALTER EVENT SESSION statement or by using the Extended Events node in Object Explorer.https://docs.microsoft.com/sql/relational-databases/system-stored-procedures/sp-server-diagnostics-transact-sql['XEvent.SPServerDiagnostics']@XEvent.SPServerDiagnosticsServer/^(Windows|Linux)$/OnPremises[11.0,)Warning
6866BlackboxTracedefinition['DefaultRuleset', 'Traces']Blackbox trace is configured and runningThis trace is designed to behave similarly to an airplane black box, to help you diagnose intermittent server crashes. It consumes more resources than the default trace and should not be running for extended periods of time.Make sure you still need the blackbox trace and stop it otherwise.https://docs.microsoft.com/sql/relational-databases/system-stored-procedures/sp-trace-create-transact-sql['CountBlackBoxTraces']Server/^(Windows|Linux)$/OnPremises[11.0,)Warning@BlackBoxTraceCount
6967DefaultTracedefinition['DefaultRuleset', 'Traces']No default trace was found or is not activeDefault trace provides troubleshooting assistance to database administrators by ensuring that they have the log data necessary to diagnose problems the first time they occur.Make sure that there is enough space for SQL Server to write the default trace file. Then have the default trace run by disabling and re-enabling it.https://docs.microsoft.com/sql/relational-databases/policy-based-management/default-trace-log-files-disabled['CountDefaultTraces']@DefaultTraceCountServer/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Warning
7068HintsStatisticsdefinition['DefaultRuleset', 'QueryOptimizer', 'Performance', 'Statistics']Hints are being usedHints are options or strategies specified for enforcement by the SQL Server query processor on SELECT, INSERT, UPDATE, or DELETE statements. The hints override any execution plan the Query Optimizer might select for a query. Because the SQL Server Query Optimizer typically selects the best execution plan for a query, we recommend that <join_hint>, <query_hint>, and <table_hint> be used only as a last resort by experienced developers and database administrators.We recommend that <join_hint>, <query_hint>, and <table_hint> be used only as a last resort by experienced developers and database administrators, because the SQL Server Query Optimizer typically selects the best execution plan for a query.https://docs.microsoft.com/sql/t-sql/queries/hints-transact-sql['Hints.InstanceStatistics']Server/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Information0
7169HintsUsageInModulesdefinition['DefaultRuleset', 'QueryOptimizer', 'Performance', 'Statistics']Hints usage in modulesHints are options or strategies specified for enforcement by the SQL Server query processor on SELECT, INSERT, UPDATE, or DELETE statements. The hints override any execution plan the Query Optimizer might select for a query. Because the SQL Server Query Optimizer typically selects the best execution plan for a query, we recommend that <join_hint>, <query_hint>, and <table_hint> be used only as a last resort by experienced developers and database administrators.@{Hint} was used in @{type_desc} @{Schema_Name}.@{Object_Name}.https://docs.microsoft.com/sql/t-sql/queries/hints-transact-sql['Hints.ModuleUsage']Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)InformationFALSE
7270PlansUseRatiodefinition['DefaultRuleset', 'Performance', 'QueryOptimizer']Amount of single use plans in cache is highSingle use plans waste system resources.Amount of single use plans in cache is high (@{SingleUsePlansUseRatio:P0}). Consider enabling the Optimize for ad hoc workloads setting on heavy OLTP ad-hoc workloads to conserve resources.https://docs.microsoft.com/sql/database-engine/configure-windows/optimize-for-ad-hoc-workloads-server-configuration-option['CachedPlans.SingleUseRatio']Server/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Warning['@SingleUsePlansUseRatio', 0.5]
7371HypotheticalIndexesdefinition['DefaultRuleset', 'Indexes', 'Performance']Hypothetical indexes foundDatabase has indexes that are marked as hypothetical. Hypothetical indexes are created by the Database Tuning Assistant (DTA) during its tests. If a DTA session was interrupted, these indexes may not be deleted. It is recommended to drop these objects as soon as possible.Index @{IndexName} for @{Schema}.@{Object} is marked as hypothetical. It is recommended to drop hypothetical index @{IndexName} as soon as possible.https://blogs.technet.microsoft.com/anurag_sharma/2008/04/15/hypothetical-indexes['Hypothetical.Indexes']Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)/^(master|model|msdb|tempdb)$/Warning
7472HypotheticalStatisticsdefinition['DefaultRuleset', 'Statistics']Hypothetical statistics foundDatabase has statistics that are marked as hypothetical. Hypothetical statistics are created by the Database Tuning Assistant (DTA) during its tests. If a DTA session was interrupted, these statistics may not be deleted. It is recommended to drop these objects as soon as possible.Statistics @{StatName} for @{Schema}.@{Object} is hypothetical. It is recommended to drop hypothetical statistics @{StatName} as soon as possible.https://blogs.technet.microsoft.com/anurag_sharma/2008/04/15/hypothetical-indexes['Hypothetical.Statistics']Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Warning
7573LatestCUdefinition['DefaultRuleset', 'Security', 'UpdateIssues']SQL Server instance is not up to dateOn an installed instance of SQL Server, we recommend that you apply the latest security updates and critical updates including general distribution releases (GDRs), service packs (SPs), and cumulative updates (CUs).Product version @{ProductVersion} is not the latest available. We recommend keeping your SQL Server up to date and install Service Packs and Cumulative Updates as they are released.https://support.microsoft.com/help/321185/how-to-determine-the-version-edition-and-update-level-of-sql-server-an, https://docs.microsoft.com/sql/database-engine/install-windows/install-sql-server-servicing-updates['SQLServerVersion']Server/^(Windows|Linux)$/OnPremises[11.0,)Warning
7674LatestCUoverrideSQL Server instance is up to dateProduct version @{ProductVersion} is the latest available.https://support.microsoft.com/help/321185/how-to-determine-the-version-edition-and-update-level-of-sql-server-an, https://docs.microsoft.com/sql/database-engine/install-windows/install-sql-server-servicing-updatesTRUEWarning['[11.0.7001, 12.0)', '[12.0.6329, 13.0)', '[13.0.5492, 14.0)', '[14.0.3238, 15.0)', '[15.0.2070,)']
7775FKNoIndexesdefinition['DefaultRuleset', 'Performance', 'Indexes']Foreign key constraints should have corresponding indexesUnlike primary key constraints, creating a foreign key constraint does not automatically create a corresponding index. However, manually creating an index on a foreign key is often useful.Create a corresponding index for each foreign key. There is no index on the following foreign keys: @{ConstraintName}.https://docs.microsoft.com/sql/relational-databases/tables/primary-and-foreign-key-constraints['FKNoIndexes']Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)/^(master|model|msdb|tempdb)$/Warning
7876MissedIndexesdefinition['DefaultRuleset', 'Performance', 'Indexes']Potentially missing indexesPotentially missing indexes were found based on query history. It may be important to revise them.Create an index on @{Table} with key columns @{KeyCols}@{IncludedCols: and included columns: #}https://docs.microsoft.com/sql/relational-databases/sql-server-index-design-guide['MissedIndexes']Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)/^(master|model|msdb|tempdb)$/Information
7977FullBackupdefinition['DefaultRuleset', 'Backup']Full backup is missed or outdatedDatabase doesn't have any full backup or the latest full backup is over 7 days.The last full backup had been created more than @{threshold} days ago. Create a new full backup.https://docs.microsoft.com/sql/relational-databases/backup-restore/create-a-full-database-backup-sql-server['DatabaseBackups']Database/^(Windows|Linux)$/OnPremises[11.0,)/^(model|tempdb)$/Warning['@LastFullBackup', {'mul': ['@threshold', 24]}]7['@LastFullBackup', None]
8078OutdatedTranLogBackupdefinition['DefaultRuleset', 'Backup']Transaction Log backup is missed or outdatedDatabase does not have any transaction Log backup since the latest full or differential backup, or it's older than 24H.Create a backup of Transaction Log. Database recovery model: @{recovery_model_desc}https://docs.microsoft.com/sql/relational-databases/backup-restore/back-up-a-transaction-log-sql-server['DatabaseBackups']Database/^(Windows|Linux)$/OnPremises[11.0,)/^(master|model|msdb|tempdb)$/Warning['@LastTLBackup', 24]['@LastTLBackup', None]
8179DbDiffCollationdefinition['DefaultRuleset', 'DBConfiguration', 'Collation']Database collation doesn't match the collation of masterWe recommend that the collations of user-defined databases match the collation of master or model. Otherwise, collation conflicts can occur that might prevent code from executing. For example, when a stored procedure joins one table to a temporary table, SQL Server might end the batch and return a collation conflict error if the collations of the user-defined database and the model database are different. This occurs because temporary tables are created in tempdb, which bases its collation on that of model.Keep database collation the same as the collation for master or modelhttps://docs.microsoft.com/sql/database-engine/set-collation-user-defined-databases-match-master-model-databases['DatabaseConfiguration']Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)['@collation_name', '@master_collation']Warning
8280AutoClosedefinition['DefaultRuleset', 'Performance', 'DBConfiguration']Auto Close Option should be OFFWhen AUTO_CLOSE is set ON, this can cause performance degradation on frequently accessed databases because of the increased overhead of opening and closing the database after each connection. AUTO_CLOSE also flushes the procedure cache after each connection.Set AUTO_CLOSE option to OFFhttps://docs.microsoft.com/sql/relational-databases/policy-based-management/set-the-auto-close-database-option-to-off['DatabaseConfiguration']Database/^(Windows|Linux)$/OnPremises[11.0,)/^(master|msdb|tempdb)$/Warning@is_auto_close_on
8381AutoShrinkdefinition['DefaultRuleset', 'DBConfiguration', 'Performance']Auto Shrink Option should be OFFShrinking databases is the fastest way to achieve fragmentation. SQL Server goes to the last page in the database, moves it to the first free available space, and then repeats the process again. This shuffles the deck, putting your pages out of order.Set AUTO_SHRINK option to OFFhttps://blogs.msdn.microsoft.com/buckwoody/2009/07/01/sql-server-best-practices-auto-shrink-should-be-off['DatabaseConfiguration']Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)/^(master|msdb|tempdb)$/Warning@is_auto_shrink_on
8482PageVerifydefinition['DefaultRuleset', 'DBConfiguration', 'DataIntegrity']PAGE_VERIFY option should be CHECKSUMWhen CHECKSUM is enabled for the PAGE_VERIFY database option, the SQL Server Database Engine calculates a checksum over the contents of the whole page, and stores the value in the page header when a page is written to disk. When the page is read from disk, the checksum is recomputed and compared to the checksum value that is stored in the page header. This helps provide a high level of data-file integrity.Set PAGE_VERIFY option to CHECKSUMhttps://docs.microsoft.com/sql/relational-databases/policy-based-management/set-the-page-verify-database-option-to-checksum['DatabaseConfiguration']Database/^(Windows|Linux)$/OnPremises[11.0,)/^(master|msdb|tempdb)$/Warning2
8583DbChainingdefinition['DefaultRuleset', 'DBConfiguration', 'Security']Cross-Database Access should be disabledOwnership chaining across databases is turned off by default. Microsoft recommends that you disable cross-database ownership chaining because it exposes you to the additional security risks.Set DB_CHAINING option to OFFhttps://docs.microsoft.com/dotnet/framework/data/adonet/sql/enabling-cross-database-access-in-sql-server['DatabaseConfiguration']Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)/^(master|msdb|tempdb)$/Warning@is_db_chaining_on
8684AutoCreateStatsIncrementaldefinition['DefaultRuleset', 'DBConfiguration', 'Statistics', 'Performance']Incremental option of auto stats should be ONIncremental statistics update at partition level is a feature introduced in SQL Server 2014. When the option INCREMENTAL is turn on at the database level, newly auto created column statistics will use incremental statistics on partitioned tables by default.Set AUTO_CREATE_STATISTICS to ON and set INCREMENTAL to ONhttps://docs.microsoft.com/sql/relational-databases/statistics/statistics['DatabaseConfiguration']@is_auto_create_stats_incremental_onDatabase/^(Windows|Linux)$/OnPremises, ManagedInstance[12.0,)/^(master|msdb|tempdb)$/Warning
8785TrustWorthydefinition['DefaultRuleset', 'DBConfiguration', 'Security']TRUSTWORTHY should be OFFYou can use the TRUSTWORTHY database setting to indicate whether the instance of Microsoft SQL Server trusts the database and the contents within the database. By default, this setting is set to OFF to mitigate certain threats that may be present when a database is attached to the server.Set TRUSTWORTHY option to OFFhttps://support.microsoft.com/help/2183687/guidelines-for-using-the-trustworthy-database-setting-in-sql-server['DatabaseConfiguration']Database/^(Windows|Linux)$/OnPremises[11.0,)/^(master|msdb|tempdb)$/Warning@is_trustworthy_on
8886ParameterizationNotSimpledefinition['DefaultRuleset', 'DBConfiguration', 'Performance', 'QueryOptimizer']PARAMETERIZATION should be SIMPLEWhen the PARAMETERIZATION database option is set to SIMPLE, the SQL Server query optimizer may choose to parameterize the queries. This means that any literal values that are contained in a query are substituted with parameters. This process is referred to as simple parameterization. When SIMPLE parameterization is in effect, you cannot control which queries are parameterized and which queries are not. However, you can specify that all queries in a database be parameterized by setting the PARAMETERIZATION database option to FORCED. Regardless of whether you have a Plan-Stability or not, SQL Server will always auto parameterize your SQL Statements, and reuse the cached execution plan over and over again. It doesn't matter how terrible the execution plan is. Therefore you have to know in exact detail the shape of your execution plans, and whether they can lead to some performance related problems.Set PARAMETERIZATION = SIMPLE and use forced parameterization only on a certain class of queries, instead of all querieshttps://docs.microsoft.com/sql/relational-databases/performance/specify-query-parameterization-behavior-by-using-plan-guides['DatabaseConfiguration']Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)/^(master|msdb|tempdb)$/Warning@is_parameterization_forced
8987TempDBFilesNotSameSizedefinition['DefaultRuleset', 'TempDB', 'Performance', 'DBFileConfiguration']TempDB data files are not the same sizeWe recommend that you create all TempDB data files at the same size.Make all TempDB data files the same sizehttps://support.microsoft.com/kb/2154845['TempDBFiles']Server/^(Windows|Linux)$/OnPremises[11.0,)Warning1
9088TempDBFilesMultiple4definition['DefaultRuleset', 'TempDB', 'Performance', 'DBFileConfiguration']Number of TempDB data files should be in multiples of 4Number of TempDB data files should correlate with the number of (logical) processors on the machine. As a general rule, if the number of logical processors is less than or equal to 8, use the same number of data files as logical processors. If the number of logical processors is greater than 8, use 8 data files and then if contention continues, increase the number of data files by multiples of 4 until the contention is reduced to acceptable levels or make changes to the workload/code.Make sure number of TempDB data files is in multiples of 4https://support.microsoft.com/kb/2154845[{'id': 'DatabaseMasterFiles', 'params': {'dbId': 2, 'type': 0}, 'transform': {'type': 'aggregate', 'map': {'physical_name': 'count'}}}, 'ServerInstanceConfiguration'][{'less': ['@online_logical_processors', 8]}, {'equal': [{'mod': ['@physical_name', 4]}, 0]}]Server/^(Windows|Linux)$/OnPremises[11.0,)Warning
9189TempDBFiles1PerCPUdefinition['DefaultRuleset', 'TempDB', 'Performance', 'DBFileConfiguration']Number of TempDB data files should depend on CPU countNumber of TempDB data files should correlate with the number of (logical) processors on the machine. As a general rule, if the number of logical processors is less than or equal to 8, use the same number of data files as logical processors. If the number of logical processors is greater than 8, use 8 data files and then if contention continues, increase the number of data files by multiples of 4 until the contention is reduced to acceptable levels or make changes to the workload/code.Make sure to have 1 data file per logical processor (processors count: @{online_logical_processors})https://support.microsoft.com/kb/2154845[{'id': 'DatabaseMasterFiles', 'params': {'dbId': 2, 'type': 0}, 'transform': {'type': 'aggregate', 'map': {'physical_name': 'count'}}}, 'ServerInstanceConfiguration'][{'greater': ['@online_logical_processors', 8]}, {'greaterequal': ['@physical_name', '@online_logical_processors']}]Server/^(Windows|Linux)$/OnPremises[11.0,)Warning
9290TempDBFilesNotLess8definition['DefaultRuleset', 'TempDB', 'Performance', 'DBFileConfiguration']Number of TempDB data files should be at least 8Number of TempDB data files should correlate with the number of (logical) processors on the machine. As a general rule, if the number of logical processors is less than or equal to 8, use the same number of data files as logical processors. If the number of logical processors is greater than 8, use 8 data files and then if contention continues, increase the number of data files by multiples of 4 until the contention is reduced to acceptable levels or make changes to the workload/code.Add extra data files to TempDB. There are @{physical_name} data files, should be at least 8https://support.microsoft.com/kb/2154845[{'id': 'DatabaseMasterFiles', 'params': {'dbId': 2, 'type': 0}, 'transform': {'type': 'aggregate', 'map': {'physical_name': 'count'}}}, 'ServerInstanceConfiguration'][{'less': ['@online_logical_processors', 9]}, {'greater': ['@physical_name', 7]}]Server/^(Windows|Linux)$/OnPremises[11.0,)Warning
9391TempDBFilesAutoGrowthdefinition['DefaultRuleset', 'TempDB', 'Performance', 'DBFileConfiguration']TempDB data files have different auto growth settingsTempDB data files should be of equal size within each filegroup, as SQL Server uses a proportional-fill algorithm that favors allocations in files with more free space.Make Autogrowth settings the same for each TempDB data filehttps://docs.microsoft.com/sql/relational-databases/databases/tempdb-database[{'id': 'DatabaseMasterFiles', 'params': {'dbId': 2, 'type': 0}, 'transform': {'type': 'aggregate', 'map': {'growth': 'count', 'is_percent_growth': 'count'}}}]Server/^(Windows|Linux)$/OnPremises[11.0,)Warning[{'@growth': 1}, {'@is_percent_growth': 1}]
9492FilesAutogrowthdefinition['DefaultRuleset', 'Performance', 'DBFileConfiguration']Database files have Autogrowth setting over 1GBA data or log file will be extended with auto-growth value to prevent the lack of free space in files. This process can perform significant impact on SQL Server performance if auto-growth value gets over 1 GB. By default, SQL Server will put zeros to a newly allocated space. And the more space it takes, the more time it takes to initialize it.Set File Growth to less than 1GB for files: @{FileName}https://support.microsoft.com/help/315512/considerations-for-the-autogrow-and-autoshrink-settings-in-sql-server['Autogrow1GB']Database/^(Windows|Linux)$/OnPremises, ManagedInstance[13.0.4001,)Warning
9593DuplicateIndexesdefinition['DefaultRuleset', 'Performance', 'Indexes']There are tables with duplicate indexesThere are tables with duplicate indexes according to their definitions. We recommended to revise all these objects as soon as possible.Consider removing duplicate indexes in table @{Table}: @{ToDelete}https://docs.microsoft.com/sql/relational-databases/sql-server-index-design-guide[{'id': 'IndexesDefinitions', 'transform': {'type': 'duplicateIndexes'}}]Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)/^(master|model|msdb|tempdb)$/Warning
9694RedundantIndexesdefinition['DefaultRuleset', 'Performance', 'Indexes']There are tables with possibly redundant indexesThere are tables with possibly redundant indexes according to the set of key and included columns. We recommended to revise all these objects as soon as possible.Consider removing redundant indexes in table @{Table}: @{Indexes}https://docs.microsoft.com/sql/relational-databases/sql-server-index-design-guide[{'id': 'IndexesDefinitions', 'transform': {'type': 'redundantIndexes'}}]Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)/^(master|model|msdb|tempdb)$/Warning
9795UserObjectsInMasterdefinition['DefaultRuleset', 'masterDB', 'Backup']User objects in database masterWe highly recommend you not create user objects in the master database. If it's unavoidable for some reason, make sure to back up the database more frequently.Remove user objects from database master: @{Object_Name}https://docs.microsoft.com/sql/relational-databases/databases/master-database['UserObjectsCountInMasterDB']Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Warningmaster
9896HighCPUUsagedefinition['DefaultRuleset', 'Performance', 'CPU']High CPU usage on serverKeeping CPU usage rates within normal ranges is vital for servers hosting SQL Server instances. A continually high rate of CPU usage may indicate the need to upgrade the CPU or add multiple processors. Alternatively, a high CPU usage rate may indicate a poorly tuned or designed application. Optimizing the application can lower CPU utilization.Investigate high CPU utilization on server hosting this instance. Last 2 hours: total CPU usage is ~@{AVGTotalCPUUsage}%, usage by SQL Server is ~@{AVGSQLCPUUsage}%https://docs.microsoft.com/sql/relational-databases/performance-monitor/monitor-cpu-usage['CpuUsage']ServerWindowsOnPremises, ManagedInstance[11.0,)Warning['@AVGTotalCPUUsage', '@threshold']70
9997ReplErrors24Hdefinition['DefaultRuleset', 'Replication']Replication errors in the last 24 hoursThis check searches for errors in distribution database agent's history table for the last 24 hours.Review replication errors for the following publications: @{publication}https://docs.microsoft.com/sql/relational-databases/replication/sql-server-replication['ReplicationErrors']Server/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Warning
10098AgentAlertsSeverity10definition['DefaultRuleset', 'Agent']Agent doesn't rise alerts for errors with severity 10Events are generated by SQL Server and entered into the Microsoft Windows application log. SQL Server Agent reads the application log and compares events written there to alerts that you have defined. When SQL Server Agent finds a match, it fires an alert, which is an automated response to an event. In addition to monitoring SQL Server events, SQL Server Agent can also monitor performance conditions and Windows Management Instrumentation (WMI) events.Consider creating alerts for the following errors: @{error_ids}https://docs.microsoft.com/sql/ssms/agent/alerts['SysAlerts'][{'in': ['@severityN', '@severity']}, {'intersect': ['@error_ids', '@message_id']}]Server/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Warning[825, 833, 855, 856, 3452, 3619, 17179, 17883, 17884, 17887, 17888, 17890, 28036]10
10199AgentAlertsSeverity16definition['DefaultRuleset', 'Agent']Agent doesn't rise alerts for errors with severity 16Events are generated by SQL Server and entered into the Microsoft Windows application log. SQL Server Agent reads the application log and compares events written there to alerts that you have defined. When SQL Server Agent finds a match, it fires an alert, which is an automated response to an event. In addition to monitoring SQL Server events, SQL Server Agent can also monitor performance conditions and Windows Management Instrumentation (WMI) events.Consider creating alerts for the following errors: @{error_ids}https://docs.microsoft.com/sql/ssms/agent/alerts['SysAlerts'][{'in': ['@severityN', '@severity']}, {'intersect': ['@error_ids', '@message_id']}]Server/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Warning[2508, 2511, 3271, 5228, 5229, 5242, 5243, 5250, 5901, 17130, 17300]16
102100AgentAlertsSeverity17definition['DefaultRuleset', 'Agent']Agent doesn't rise alerts for errors with severity 17Events are generated by SQL Server and entered into the Microsoft Windows application log. SQL Server Agent reads the application log and compares events written there to alerts that you have defined. When SQL Server Agent finds a match, it fires an alert, which is an automated response to an event. In addition to monitoring SQL Server events, SQL Server Agent can also monitor performance conditions and Windows Management Instrumentation (WMI) events.Consider creating alerts for the following errors: @{error_ids}https://docs.microsoft.com/sql/ssms/agent/alerts['SysAlerts'][{'in': ['@severityN', '@severity']}, {'intersect': ['@error_ids', '@message_id']}]Server/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Warning[802, 845, 1101, 1105, 1121, 1214, 8642, 9002]17
103101AgentAlertsSeverity19definition['DefaultRuleset', 'Agent']Agent doesn't rise alerts for errors with severity 19Events are generated by SQL Server and entered into the Microsoft Windows application log. SQL Server Agent reads the application log and compares events written there to alerts that you have defined. When SQL Server Agent finds a match, it fires an alert, which is an automated response to an event. In addition to monitoring SQL Server events, SQL Server Agent can also monitor performance conditions and Windows Management Instrumentation (WMI) events.Consider creating alerts for the following errors: @{error_ids}https://docs.microsoft.com/sql/ssms/agent/alerts['SysAlerts'][{'in': ['@severityN', '@severity']}, {'intersect': ['@error_ids', '@message_id']}]Server/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Warning[701]19
104102AgentAlertsSeverity20definition['DefaultRuleset', 'Agent']Agent doesn't rise alerts for errors with severity 20Events are generated by SQL Server and entered into the Microsoft Windows application log. SQL Server Agent reads the application log and compares events written there to alerts that you have defined. When SQL Server Agent finds a match, it fires an alert, which is an automated response to an event. In addition to monitoring SQL Server events, SQL Server Agent can also monitor performance conditions and Windows Management Instrumentation (WMI) events.Consider creating alerts for the following errors: @{error_ids}https://docs.microsoft.com/sql/ssms/agent/alerts['SysAlerts'][{'in': ['@severityN', '@severity']}, {'intersect': ['@error_ids', '@message_id']}]Server/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Warning[3624]20
105103AgentAlertsSeverity21definition['DefaultRuleset', 'Agent']Agent doesn't rise alerts for errors with severity 21Events are generated by SQL Server and entered into the Microsoft Windows application log. SQL Server Agent reads the application log and compares events written there to alerts that you have defined. When SQL Server Agent finds a match, it fires an alert, which is an automated response to an event. In addition to monitoring SQL Server events, SQL Server Agent can also monitor performance conditions and Windows Management Instrumentation (WMI) events.Consider creating alerts for the following errors: @{error_ids}https://docs.microsoft.com/sql/ssms/agent/alerts['SysAlerts'][{'in': ['@severityN', '@severity']}, {'intersect': ['@error_ids', '@message_id']}]Server/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Warning[605]21
106104AgentAlertsSeverity22definition['DefaultRuleset', 'Agent']Agent doesn't rise alerts for errors with severity 22Events are generated by SQL Server and entered into the Microsoft Windows application log. SQL Server Agent reads the application log and compares events written there to alerts that you have defined. When SQL Server Agent finds a match, it fires an alert, which is an automated response to an event. In addition to monitoring SQL Server events, SQL Server Agent can also monitor performance conditions and Windows Management Instrumentation (WMI) events.Consider creating alerts for the following errors: @{error_ids}https://docs.microsoft.com/sql/ssms/agent/alerts['SysAlerts'][{'in': ['@severityN', '@severity']}, {'intersect': ['@error_ids', '@message_id']}]Server/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Warning[5180, 8966]22
107105AgentAlertsSeverity23definition['DefaultRuleset', 'Agent']Agent doesn't rise alerts for errors with severity 23Events are generated by SQL Server and entered into the Microsoft Windows application log. SQL Server Agent reads the application log and compares events written there to alerts that you have defined. When SQL Server Agent finds a match, it fires an alert, which is an automated response to an event. In addition to monitoring SQL Server events, SQL Server Agent can also monitor performance conditions and Windows Management Instrumentation (WMI) events.Consider creating alerts for the following errors: @{error_ids}https://docs.microsoft.com/sql/ssms/agent/alerts['SysAlerts'][{'in': ['@severityN', '@severity']}, {'intersect': ['@error_ids', '@message_id']}]Server/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Warning[5572, 9100]23
108106AgentAlertsSeverity24definition['DefaultRuleset', 'Agent']Agent doesn't rise alerts for errors with severity 24Events are generated by SQL Server and entered into the Microsoft Windows application log. SQL Server Agent reads the application log and compares events written there to alerts that you have defined. When SQL Server Agent finds a match, it fires an alert, which is an automated response to an event. In addition to monitoring SQL Server events, SQL Server Agent can also monitor performance conditions and Windows Management Instrumentation (WMI) events.Consider creating alerts for the following errors: @{error_ids}https://docs.microsoft.com/sql/ssms/agent/alerts['SysAlerts'][{'in': ['@severityN', '@severity']}, {'intersect': ['@error_ids', '@message_id']}]Server/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Warning[823, 824, 832]24
109107WeakPassworddefinition['DefaultRuleset', 'Security', 'WeakPassword']Weak passwordSome user logins have weak passwords.Make sure to set strong passwords on the following logins: @{PasswordData}https://docs.microsoft.com/sql/relational-databases/security/strong-passwords['WeakPassword']Server/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Warning
110108VLFCountdefinition['DefaultRuleset', 'Backup', 'Performance']VLF countThe SQL Server Database Engine divides each physical log file internally into a number of virtual log files (VLFs). Virtual log files have no fixed size, and there is no fixed number of virtual log files for a physical log file. The Database Engine chooses the size of the virtual log files dynamically while it is creating or extending log files. The Database Engine tries to maintain a small number of virtual files. The size of the virtual files after a log file has been extended is the sum of the size of the existing log and the size of the new file increment. The size or number of virtual log files cannot be configured or set by administrators. If the log files grow to a large size in many small increments, they will have many virtual log files. This can slow down database startup and also log backup and restore operations. Conversely, if the log files are set to a large size with few or just one increment, they will have few very large virtual log files. We recommend that you assign log files a size value close to the final size required, using the required increments to achieve optimal VLF distribution, and also have a relatively large growth_increment value.Update transaction log settings to reduce the number of VLFs (current number is: @{RecoveryUnitId})https://docs.microsoft.com/sql/relational-databases/sql-server-transaction-log-architecture-and-management-guide[{'id': 'VLF', 'transform': {'type': 'aggregate', 'map': {'RecoveryUnitId': {'type': 'count', 'distinct': False}}}}]Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Warning['@RecoveryUnitId', '@threshold']50
111109TF8015definition['DefaultRuleset', 'TraceFlag', 'CPU', 'NUMA']TF 8015 disables auto-detection and NUMA setupSQL Server allows you to group CPUs into nodes referred to as soft-NUMA. You usually configure soft-NUMA when you have many CPUs and do not have hardware NUMA, but you can also use soft-NUMA to subdivide hardware NUMA nodes into smaller groups.Disable trace flag 8015 for this SQL Server instance. This TF does not apply to this SQL Server versionhttps://techcommunity.microsoft.com/t5/SQL-Server-Support/How-It-Works-Soft-NUMA-I-O-Completion-Thread-Lazy-Writer-Workers/ba-p/316044['EnabledGlobalTraceFlags']ServerWindowsOnPremises[11.0,11.0.3349)Warning[8015, '@TraceFlag']
112110TF8032definition['DefaultRuleset', 'TraceFlag', 'Performance']TF 8032 reverts the cache limit parameters to the SQL Server 2005 RTMTrace Flag 8032 reverts the cache limit parameters to the SQL Server 2005 RTM setting but can cause poor performance if large caches make less memory available for other memory consumers like BP.The cache limit parameters reverted to the SQL Server 2005 RTM setting but can cause poor performance if large caches make less memory available for other memory consumers like BP['EnabledGlobalTraceFlags']ServerWindowsOnPremises[11.0,)Warning[8032, '@TraceFlag']
113111TF8744definition['DefaultRuleset', 'TraceFlag', 'Performance']TF 8744 disables pre-fetching for the Nested Loop operatorTrace flag 8744 disables pre-fetching for the Nested Loops operator. Incorrect use of this trace flag may cause additional physical reads when SQL Server executes plans that contain the Nested Loops operator.Disable trace flag 8744 for this SQL Server instance. This TF does not apply to this SQL Server versionhttps://support.microsoft.com/help/920093/tuning-options-for-sql-server-when-running-in-high-performance-workloa['EnabledGlobalTraceFlags']ServerWindowsOnPremises[11.0,12.0)Warning[8744, '@TraceFlag']
114112TF9347definition['DefaultRuleset', 'TraceFlag', 'Performance']TF 9347 disables batch mode for sort operatorTrace flag 9347 disables batch mode for sort operator. SQL Server 2016 (13.x) introduced a new batch mode sort operator that boosts performance for many analytical queries.Disable trace flag 9347 for this SQL Server instance. This TF does not apply to this SQL Server version['EnabledGlobalTraceFlags']ServerWindowsOnPremises[11.0,13.0)Warning[9347, '@TraceFlag']
115113TF9349definition['DefaultRuleset', 'TraceFlag', 'Performance']TF 9349 disables batch mode for top N sort operatorTrace flag 9349 disables batch mode for top N sort operator. SQL Server 2016 (13.x) introduced a new batch mode top sort operator that boosts performance for many analytical queries.Disable trace flag 9349 for this SQL Server instance. This TF does not apply to this SQL Server version['EnabledGlobalTraceFlags']ServerWindowsOnPremises[11.0,13.0)Warning[9349, '@TraceFlag']
116114TF9389definition['DefaultRuleset', 'TraceFlag', 'Performance', 'TempDB']TF 9389 enables dynamic memory grant for batch mode operatorsTrace flag 9389 enables additional dynamic memory grant for batch mode operators. If a query does not get all the memory it needs, it spills data to TempDB, incurring additional I/O and potentially impacting query performance. If the dynamic memory grant trace flag is enabled, a batch mode operator may ask for additional memory and avoid spilling to TempDB if additional memory is available.Disable trace flag 9389 for this SQL Server instance. The TF does not apply to this SQL Server version['EnabledGlobalTraceFlags']ServerWindowsOnPremises, ManagedInstance[11.0,13.0)Warning[9389, '@TraceFlag']
117115TF9476definition['DefaultRuleset', 'TraceFlag', 'Performance', 'QueryOptimizer']TF 9476 causes SQL Server to generate a plan using the Simple Containment instead of the default Base Containment under New CETrace flag 9476 causes SQL Server to generate a plan using the Simple Containment assumption instead of the default Base Containment assumption, under the query optimizer cardinality estimation model of SQL Server 2014 (12.x) through SQL Server 2017 versions.Disable trace flag 9476 for this SQL Server instance. The TF does not apply to this SQL Server version['EnabledGlobalTraceFlags']ServerWindowsOnPremises[11.0,13.0)Warning[9476, '@TraceFlag']
118116TF9481definition['DefaultRuleset', 'TraceFlag', 'QueryOptimizer', 'Performance']TF 9481 enables Legacy CE model, irrespective of the compatibility level of the databaseTrace flag 9481 enables you to set the query optimizer cardinality estimation model to the SQL Server 2012 (11.x) and earlier versions, irrespective of the compatibility level of the database.Disable trace flag 9481 for this SQL Server instance. The TF does not apply to this SQL Server version['EnabledGlobalTraceFlags']ServerWindowsOnPremises[11.0,12.0)Warning[9481, '@TraceFlag']
119117TF10204definition['DefaultRuleset', 'TraceFlag', 'Performance', 'ColumnStore']TF 10204 disables merge/recompress during columnstore index reorganizationTrace flag 10204 disables merge/recompress during columnstore index reorganization. In SQL Server 2016 (13.x), when a columnstore index is reorganized, there is new functionality to automatically merge any small compressed rowgroups into larger compressed rowgroups, as well as recompressing any rowgroups that have a large number of deleted rows.Disable trace flag 10204 for this SQL Server instance. The TF does not apply to this SQL Server version['EnabledGlobalTraceFlags']ServerWindowsOnPremises[11.0,13.0)Warning[10204, '@TraceFlag']
120118SPNamingdefinition['DefaultRuleset', 'Naming']Stored Procedure NamingIn SQL Server, the sp_ prefix designates system stored procedures. If you use that prefix for your stored procedures, the name of your procedure might conflict with the name of a system stored procedure that will be created in the future. If such a conflict occurs, your application might break if your application refers to the procedure without qualifying the reference by schema. In this situation, the name will bind to the system procedure instead of to your procedure.Rename the following stored procedures to get rid of the sp_ prefix: @{ObjectName}https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/dd172115(v=vs.100)['BadNamingSP']Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Warning@ObjectName
121119ObjectNamingSpecialChardefinition['DefaultRuleset', 'Naming']Object NamingIf you name a database object by using any character in the following table, you make it more difficult not only to reference that object but also to read code that contains the name of that object.Rename the following objects to get rid of special characters: @{ObjectName}https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/dd172134(v=vs.100)['BadNamingSpecialChars']Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Warning@ObjectName
122120ColumnNamingSpecialChardefinition['DefaultRuleset', 'Naming']Column NamingIf you name a database object by using any character in the following table, you make it more difficult not only to reference that object but also to read code that contains the name of that object.Rename the following columns to get rid of special characters: @{ObjectName}https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/dd172134(v=vs.100)['BadNamingSpecialCharsColumns']Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Warning@ObjectName
123121FnNamingdefinition['DefaultRuleset', 'Naming']User Function NamingIn SQL Server, the fn_ prefix designates system functions. If you use that prefix for your functions, the name of your function might conflict with the name of a system function that will be created in the future. If such a conflict occurs, your application might break if your application refers to the function without qualifying the reference by schema. In this situation, the name will bind to the system function instead of to your function.Rename the following functions to get rid of the fn_ prefix: @{ObjectName}https://docs.microsoft.com/sql/t-sql/statements/create-function-transact-sql['BadNamingUserFunctions']Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Warning@ObjectName
124122ObjectNamingResKeywordsdefinition['DefaultRuleset', 'Naming']Object names contain reserved keywordsMicrosoft SQL Server uses reserved keywords for defining, manipulating, and accessing databases. Reserved keywords are part of the grammar of the Transact-SQL language that is used by SQL Server to parse and understand Transact-SQL statements and batches. Although it is syntactically possible to use SQL Server reserved keywords as identifiers and object names in Transact-SQL scripts, you can do this only by using delimited identifiers.Rename the following objects to get rid of reserved keywords: @{ObjectName}https://docs.microsoft.com/sql/t-sql/language-elements/reserved-keywords-transact-sql['BadNamingKeywords']Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Warning@ObjectName
125123DeprFeaturesInModulesdefinition['DefaultRuleset', 'Security', 'Deprecated', 'LongRunningChecks', 'UpdateIssues']Use of deprecated or discontinued features in modulesDeprecated features are scheduled to be removed in a future release of SQL Server. Discontinued features have been removed from specific versions of SQL Server.Consider getting rid of the following deprecated or discontinued features in @{ObjectName}: @{Keyword}https://docs.microsoft.com/sql/relational-databases/performance-monitor/sql-server-deprecated-features-object['DeprecatedFeaturesSQLModules']Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)/^(master|tempdb|model|msdb)$/Warning
126124DeprFeaturesInJobsdefinition['DefaultRuleset', 'Security', 'Deprecated', 'Agent', 'Jobs', 'LongRunningChecks', 'UpdateIssues']Use of deprecated or discontinued features in modulesDeprecated features are scheduled to be removed in a future release of SQL Server. Discontinued features have been removed from specific versions of SQL Server.Consider getting rid of the following deprecated or discontinued features in job @{ObjectName}: @{Keyword}https://docs.microsoft.com/sql/relational-databases/performance-monitor/sql-server-deprecated-features-object['DeprecatedFeaturesJobs']Server/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Warning
127125NUMANodeSingleCPUdefinition['DefaultRuleset', 'NUMA', 'CPU', 'Memory', 'Performance']Single CPU assigned to NUMA nodeMicrosoft SQL Server is non-uniform memory access (NUMA) aware. NUMA architecture provides a scalable solution to performance problem. Computers with hardware NUMA have more than one system bus, each serving a small set of processors. Each group of processors has its own memory and possibly its own I/O channels, but each CPU can access memory associated with other groups in a coherent way. Each group is called a NUMA node. The number of CPUs within a NUMA node depends on the hardware vendor. Your hardware manufacturer can tell you if your computer supports hardware NUMA.Consider assigning additional CPUs to NUMA nodes that have only one assigned CPUhttps://docs.microsoft.com/previous-versions/sql/sql-server-2008-r2/ms178144(v=sql.105)['ServerInstanceConfiguration']ServerWindowsOnPremises, ManagedInstance[11.0,)Warning@nodes_single_cpu
128126NUMANodeNoCPUdefinition['DefaultRuleset', 'NUMA', 'Performance', 'CPU', 'Memory']NUMA nodes without CPUsMicrosoft SQL Server is non-uniform memory access (NUMA) aware. NUMA architecture provides a scalable solution to performance problem. Computers with hardware NUMA have more than one system bus, each serving a small set of processors. Each group of processors has its own memory and possibly its own I/O channels, but each CPU can access memory associated with other groups in a coherent way. Each group is called a NUMA node. The number of CPUs within a NUMA node depends on the hardware vendor. Your hardware manufacturer can tell you if your computer supports hardware NUMA.Make sure that all NUMA nodes have assigned CPUshttps://docs.microsoft.com/previous-versions/sql/sql-server-2008-r2/ms178144(v=sql.105)['AffinityNUMANodeNoAssignedCPUs']ServerWindowsOnPremises, ManagedInstance[11.0,)Warning@NodeCnt
129127IndexKeyGuiddefinition['DefaultRuleset', 'Indexes', 'Performance']Guid in clustered index key columnA big reason for a clustered index is when you often want to retrieve rows for a range of values for a given column. Because the data is physically arranged in that order, the rows can be extracted very efficiently. Something like a GUID, while excellent for a primary key, could be positively detrimental to performance, as there will be additional cost for inserts and no perceptible benefit on selects.Get rid of GUIDs in the following clustered indexes' keys: @{IndexName}https://azure.microsoft.com/blog/uniqueidentifier-and-clustered-indexes/['IndexesGuidKeyColumns']Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)/^(master|tempdb|model|msdb)$/Warning
130128IndexesLargeKeysdefinition['DefaultRuleset', 'Indexes', 'Performance']Indexes keys with more than 900 bytesWhen you design an index that contains many key columns, or large-size columns, calculate the size of the index key to make sure that you do not exceed the maximum index key size. SQL Server retains the 900-byte limit for the maximum total size of all index key columns. This excludes nonkey columns that are included in the definition of nonclustered indexes.Get rid of keys larger than 900 bytes in index @{FullName}http://msdn.microsoft.com/library/ms191241.aspx['IndexesDefinitions']Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,13.0)/^(master|model|msdb|tempdb)$/Warning['@KeySize', 900]
131129IndexesLargeKeysNonClustdefinition['DefaultRuleset', 'Indexes', 'Performance']NonClustered indexes keys with more than 1700 bytesWhen you design an index that contains many key columns, or large-size columns, calculate the size of the index key to make sure that you do not exceed the maximum index key size. SQL Server retains the 1700-byte limit for the maximum total size of all non-clustered index key columns. This excludes nonkey columns that are included in the definition of nonclustered indexes.Get rid of keys larger than 1700 bytes in index @{FullName}http://msdn.microsoft.com/library/ms191241.aspx['IndexesDefinitions'][{'le': ['@KeySize', 1700]}, {'not': {'in': ['@Type', [2, 6]]}}]Database/^(Windows|Linux)$/OnPremises, ManagedInstance[13.0,)/^(master|model|msdb|tempdb)$/Warning
132130IndexesLargeKeysClustdefinition['DefaultRuleset', 'Indexes', 'Performance']Clustered indexes keys with more than 900 bytesWhen you design an index that contains many key columns, or large-size columns, calculate the size of the index key to make sure that you do not exceed the maximum index key size. SQL Server retains the 900-byte limit for the maximum total size of all clustered index key columns. This excludes nonkey columns that are included in the definition of nonclustered indexes.Get rid of keys larger than 900 bytes in index @{FullName}http://msdn.microsoft.com/library/ms191241.aspx['IndexesDefinitions'][{'le': ['@KeySize', 900]}, {'not': {'in': ['@Type', [1, 5]]}}]Database/^(Windows|Linux)$/OnPremises, ManagedInstance[13.0,)/^(master|model|msdb|tempdb)$/Warning
133131DisabledIndexesdefinition['DefaultRuleset', 'Indexes', 'Performance']Disabled Indexes existIf you need to load a lot of data quickly, you can disable nonclustered indexes in order to improve performance. After the data load finishes, enable the nonclustered indexes again by rebuilding them. This technique works best in large data warehouse environments where entire dimension tables might be reloaded from scratch every night. Disabling nonclustered indexes is safer than dropping and recreating them because scripting indexes is hard. Unfortunately, sometimes our load processes crash before enabling the indexes again, or sometimes we manually load data and we forget to rebuild them.Remove or enable this disabled index: @{FullName}https://docs.microsoft.com/sql/relational-databases/indexes/disable-indexes-and-constraints['IndexesDefinitions']Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)/^(master|model|msdb|tempdb)$/WarningFALSE
134132IndexesFillFactordefinition['DefaultRuleset', 'Indexes', 'Performance']Index fill factor lower 80%The fill-factor option is provided for fine-tuning index data storage and performance. When an index is created or rebuilt, the fill-factor value determines the percentage of space on each leaf-level page to be filled with data, reserving the remainder on each page as free space for future growth. For example, specifying a fill-factor value of 80 means that 20 percent of each leaf-level page will be left empty, providing space for index expansion as data is added to the underlying table. The empty space is reserved between the index rows rather than at the end of the index.Review index @{FullName} as its fill factor @{FillFactor} is lower than 80 percenthttps://docs.microsoft.com/sql/relational-databases/indexes/specify-fill-factor-for-an-index['IndexesDefinitions'][{'less': ['@FillFactor', 1]}, {'ge': ['@FillFactor', 80]}]Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)/^(master|model|msdb|tempdb)$/Warning
135133NonUniqueClusterIndexdefinition['DefaultRuleset', 'Indexes', 'Performance']Non-unique clustered indexesIndex uniqueness is highly desirable attribute of a clustering key, and goes hand-in-hand with index narrowness. SQL Server does not require a clustered index to be unique, but yet it must have some means of uniquely identifying every row. That’s why, for non-unique clustered indexes, SQL Server adds to every duplicate instance of a clustering key value a 4-byte integer value called a uniqueifier. This uniqueifier is added everywhere the clustering key is stored. That means the uniqueifier is stored in both clustered and non-clustered indexes. As you can imagine, if there are many rows using the same clustering key value, this can become quite expensive.Review this clustered index @{FullName} as it is non-uniquehttps://docs.microsoft.com/sql/relational-databases/indexes/clustered-and-nonclustered-indexes-described['IndexesDefinitions'][{'gt': ['@Type', 1]}, {'@IsUnique': True}]Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)/^(master|model|msdb|tempdb)$/Warning
136134SuspectPagesdefinition['DefaultRuleSet', 'Pages', 'DataIntegrity']Suspect pagesThe suspect_pages table is used for maintaining information about suspect pages, and is relevant in helping to decide whether a restore is necessary.Run DBCC CHECKDB to verify affected database. Suspect pages were found: @{EventType}https://docs.microsoft.com/sql/relational-databases/backup-restore/manage-the-suspect-pages-table-sql-server['SuspectPagesValidation']Database/^(Windows|Linux)$/[11.0,)Warning
137135SparseFilesdefinition['DefaultRuleSet', 'Snapshots', 'Backup', 'DataIntegrity']Sparse filesIf the file is sparse or compressed, the NTFS file system may deallocate disk space in the file. This sets the range of bytes to zeroes (0) without extending the file size.Get rid of sparse files: @{SparseFiles}https://blogs.msdn.microsoft.com/jorgepc/2010/11/25/what-are-sparse-files-and-why-should-i-care-as-sql-server-dba/, https://techcommunity.microsoft.com/t5/SQL-Server-Support/Did-your-backup-program-utility-leave-your-SQL-Server-running-in/ba-p/315840['SparseFilesValidation']Database/^(Windows|Linux)$/[11.0,)Warning
138136TableNoIndexdefinition['DefaultRuleset', 'Indexes', 'Performance']Tables without indexesEach table in the database has one or more pages. To keep track of those pages, SQL Server uses a special set of pages, called IAM (for Index Allocation Map) pages. In spite of the word “Index” in the name, IAMs are used for non-indexed tables as well. These are called heaps. All the data is there, but the only way to find anything is to read it starting at the beginning. For a very large table, this will be terribly inefficient.Review table @{TableName} and create reasonable indexeshttps://docs.microsoft.com/sql/relational-databases/indexes/heaps-tables-without-clustered-indexes['TableIndexes'][{'gt': ['@IndexCount', 1]}, {'gt': ['@MaxIndexId', 0]}]Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)/^(master|tempdb|model|msdb)$/Warning
139137TableNoClusteredIndexdefinition['DefaultRuleset', 'Indexes', 'Performance']Tables without clustered indexesTables without clustered indexes are called heaps. They’re scattered on disk anywhere that SQL Server can find a spot, and they’re not stored in any order whatsoever. This can make for really fast inserts – SQL Server can just throw the data down – but slow selects, updates, and deletes.Review table @{TableName} and consider creating a clustered indexhttps://docs.microsoft.com/sql/relational-databases/indexes/heaps-tables-without-clustered-indexes['TableIndexes'][{'le': ['@IndexCount', 1]}, {'gt': ['@MinIndexId', 0]}]Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)/^(master|tempdb|model|msdb)$/Warning
140138TablePSAligndefinition['DefaultRuleset', 'Indexes', 'Performance']Table index not aligned with PSTable partitioning is a complex way to break out your large tables into smaller, more manageable chunks, but it comes with a lot of management heartache. One of the challenges is making sure that your indexes are partitioned and aligned the same way as your clustered index.Consider recreating index @{IndexName} in table @{TableName} to have it aligned with your schemahttps://docs.microsoft.com/sql/relational-databases/partitions/partitioned-tables-and-indexes['TableIndexesPartitioned']Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)/^(master|tempdb|model|msdb)$/Warning
141139LoginNoPassworddefinition['DefaultRuleset', 'Security', 'WeakPassword']Logins with no passwordsPassword complexity policies are designed to deter brute force attacks by increasing the number of possible passwords.Make sure to set strong passwords on the following logins: @{PasswordData}https://docs.microsoft.com/sql/relational-databases/security/password-policy['NullPassword']Server/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Warning
142140LoginEqPassworddefinition['DefaultRuleset', 'Security', 'WeakPassword']Logins with passwords that are same as the login namesPassword complexity policies are designed to deter brute force attacks by increasing the number of possible passwords.Please review logins with password equals to login: @{PasswordData}https://docs.microsoft.com/sql/relational-databases/security/password-policy['NamePassword']Server/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Warning
143141SystemHealthdefinition['DefaultRuleset', 'XEvent', 'SystemHealth', 'Performance']System Health important messagesThe system_health session is an Extended Events session that is included by default with SQL Server. This session starts automatically when the SQL Server Database Engine starts, and runs without any noticeable performance effects. The session collects system data that you can use to help troubleshoot performance issues in the Database EngineError @{Error_Number} has occured @{Error_Count} times. Last time was @{Last_Logged_Days_Ago} days agohttps://docs.microsoft.com/sql/relational-databases/extended-events/use-the-system-health-session['SystemHealth']Server/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)Warning
144142RarelyUsedIndexdefinition['DefaultRuleset', 'Indexes', 'Performance']Rarely used indexRarely used indexes can slow down database's performance. Time of write operations is increased because of index maintenance, but index is not used quite often. It makes sense to compare impact of writing operations versus rare reading speedup.Make sure you need index @{IndexName} as it's used too rarelyhttps://docs.microsoft.com/sql/t-sql/statements/drop-index-transact-sql['IndexesDefinitions'][{'@Hits': 0}, {'ge': ['@ReadsRatio', '@ReadsThreshold']}, {'@IsPrimaryKey': True}]Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)/^(master|model|msdb|tempdb)$/Warning5
145143UnusedIndexdefinition['DefaultRuleset', 'Index', 'Performance']Unused indexUnused indexes can slow down database's performance. Time of write operations is increased because of index maintenance, but index is not used anywhere.Make sure you need index @{IndexName} as it's unusedhttps://docs.microsoft.com/sql/t-sql/statements/drop-index-transact-sql['IndexesDefinitions'][{'and': [{'ne': ['@Type', 2]}, {'ne': ['@Type', 6]}]}, {'@IsPrimaryKey': True}, {'gt': ['@Hits', 0]}]Database/^(Windows|Linux)$/OnPremises, ManagedInstance[11.0,)/^(master|model|msdb|tempdb)$/Warning
146144SkewedCompatibilityLeveldefinition['DefaultRuleset', 'CompatibilityLevel', 'Security', 'Performance', 'UpdateIssues']Database with skewed compatibility levelSome databases may have a compatibility level lower than the allowed level by the Database Engine.Update database compatibility level (current level: @{CompatibilityLevel})https://docs.microsoft.com/sql/t-sql/statements/alter-database-transact-sql-compatibility-level['CompatibilityLevel', 'SQLServerVersion']Database/^(Windows|Linux)$/[11.0,)Warning[{'div': ['@CompatibilityLevel', 10]}, '@ServerMajorVersion']
Reference in New Issue View Git Blame Copy Permalink