Update SQL Assessment API docs for v 1.1.17

samples/manage/sql-assessment-api/DefaultRuleset.csv

@@ -193,15 +193,15 @@
 "MaxDopFewNumaLess16","definition","TRUE","Low","MAXDOP set in accordance with CPU count","Update MAXDOP configuration option value: @{max_dop}. It should not exceed the number of logical processors per NUMA node","DefaultRuleset, MaxDOP, Performance, Configuration, NUMA, CPU","The Microsoft SQL Server max degree of parallelism (MAXDOP) configuration option controls the number of processors that are used for the execution of a query in a parallel plan. This option determines the number of threads that are used for the query plan operators that perform the work in parallel. Depending on whether SQL Server is set up on a symmetric multiprocessing (SMP) computer, a non-uniform memory access (NUMA) computer, or hyperthreading-enabled processors, the max degree of parallelism option should be configured appropriately.","https://support.microsoft.com/kb/2806535","Server","Windows Linux",,"SqlServer","[13.0,)",,,
 "MaxDopFewNumaOver16","definition","TRUE","Low","MAXDOP set in accordance to CPU count","Update MAXDOP configuration option value: @{max_dop}. It should be half the number of logical processors per NUMA node with maximum value of 16","DefaultRuleset, MaxDOP, Performance, Configuration, NUMA, CPU","The Microsoft SQL Server max degree of parallelism (MAXDOP) configuration option controls the number of processors that are used for the execution of a query in a parallel plan. This option determines the number of threads that are used for the query plan operators that perform the work in parallel. Depending on whether SQL Server is set up on a symmetric multiprocessing (SMP) computer, a non-uniform memory access (NUMA) computer, or hyperthreading-enabled processors, the max degree of parallelism option should be configured appropriately.","https://support.microsoft.com/kb/2806535","Server","Windows Linux",,"SqlServer","[13.0,)",,,
 "MaxDopFewNumaOver8","definition","TRUE","Medium","MAXDOP set in accordance with CPU count","Update MAXDOP configuration option value: @{max_dop}. It should be equal to 8","DefaultRuleset, MaxDOP, Performance, Configuration, NUMA, CPU","The Microsoft SQL Server max degree of parallelism (MAXDOP) configuration option controls the number of processors that are used for the execution of a query in a parallel plan. This option determines the number of threads that are used for the query plan operators that perform the work in parallel. Depending on whether SQL Server is set up on a symmetric multiprocessing (SMP) computer, a non-uniform memory access (NUMA) computer, or hyperthreading-enabled processors, the max degree of parallelism option should be configured appropriately.","https://support.microsoft.com/kb/2806535","Server","Windows",,"SqlServer","[11.0, 13.0)",,,
-"MaxMemory","definition","TRUE","Low","Max allowed memory ","Set 'max server memory' value to @{recommended:N0} MB or less to avoid detrimental memory pressure. Current 'max server memory' value is @{max_server_memory:N0}, which is greater than recommended","DefaultRuleset, Memory, Performance, MaxMemory","Setting the 'max server memory' value too high can cause a single instance of SQL Server to compete for memory with other SQL Server instances hosted on the same machine. However, setting this value too low could cause significant memory pressure and performance problems.","https://docs.microsoft.com/sql/database-engine/configure-windows/server-memory-server-configuration-options","Server","Windows Linux",,"SqlServer","[11.0,)",,,"2147483647"
+"MaxMemory","definition","TRUE","Low","Max allowed memory ","Set 'max server memory (MB)' value to @{recommended:N0} MB or less to avoid detrimental memory pressure. Current 'max server memory (MB)' value is @{max_server_memory:N0}, which is greater than recommended","DefaultRuleset, Memory, Performance, MaxMemory","Setting the 'max server memory (MB)' value too high can cause a single instance of SQL Server to compete for memory with other SQL Server instances hosted on the same machine. However, setting this value too low could cause significant memory pressure and performance problems.","https://docs.microsoft.com/sql/database-engine/configure-windows/server-memory-server-configuration-options","Server","Windows Linux",,"SqlServer","[11.0,)",,,"2147483647"
 "MaxMemory","override","TRUE","Low",,,"",,,,,,"Express",,,,"1410"
 "MaxMemory","override","TRUE","Low",,,"",,,,,,"Standard",,,,"131072"
-"MaxMemorySystem","definition","TRUE","Low","Max server memory exceeds system memory","Set 'max server memory' to @{recommended:N0} MB or less to avoid detrimental memory pressure. System memory of @{sysmem:N0} MB is not sufficient for current 'max server memory' setting of @{max_server_memory:N0} MB","DefaultRuleset, Memory, Performance, MaxMemory","Setting the 'max server memory' value higher than system memory can cause SQL Server to compete for memory with the operating system and processes running on the same machine.","https://docs.microsoft.com/sql/database-engine/configure-windows/server-memory-server-configuration-options","Server","Windows Linux",,"SqlServer","[11.0,)",,,"2147483647"
+"MaxMemorySystem","definition","TRUE","Low","Max server memory exceeds system memory","Set 'max server memory (MB)' to @{recommended:N0} MB or less to avoid detrimental memory pressure. System memory of @{sysmem:N0} MB is not sufficient for current 'max server memory (MB)' setting of @{max_server_memory:N0} MB","DefaultRuleset, Memory, Performance, MaxMemory","Setting the 'max server memory (MB)' value higher than system memory can cause SQL Server to compete for memory with the operating system and processes running on the same machine.","https://docs.microsoft.com/sql/database-engine/configure-windows/server-memory-server-configuration-options","Server","Windows Linux",,"SqlServer","[11.0,)",,,"2147483647"
 "MaxMemorySystem","override","TRUE","Low",,,"",,,,,,"Express",,,,"1410"
 "MaxMemorySystem","override","TRUE","Low",,,"",,,,,,"Standard",,,,"131072"
 "MinMemoryPerQuery","definition","TRUE","Low","Option 'min memory per query' set to default","Set 'min memory per query' option to @{recommended_min_memory_per_query} KB. Current value is '@{min_memory_per_query}'","DefaultRuleset, Configuration, Memory, Performance","The min memory per query option specifies the minimum amount of memory (in kilobytes) that will be allocated for the execution of a query. This is also known as the minimum memory grant. The default value is 1,024 KB. Do not set the min memory per query server configuration option too high, especially on very busy systems, because the query has to wait1 until it can secure the minimum memory requested, or until the value specified in the query wait server configuration option is exceeded. If more memory is available than the specified minimum value required to execute the query, the query is allowed to make use of the additional memory, provided that the memory can be used effectively by the query.","https://docs.microsoft.com/sql/database-engine/configure-windows/configure-the-min-memory-per-query-server-configuration-option","Server","Windows Linux",,"SqlServer","[11.0,)",,,
 "NetworkPacketSize","definition","TRUE","Low","Option 'network packet size' set to default","Set 'network packet size' option to @{recommended_network_packet_size} bytes. Current value is @{network_packet_size}","DefaultRuleset, Configuration, Network","The 'network packet size' option sets the packet size (in bytes) that is used across the whole network. Packets are the fixed-size chunks of data that transfer requests and results between clients and servers. The default packet size is 4096 bytes.","https://docs.microsoft.com/sql/database-engine/configure-windows/configure-the-network-packet-size-server-configuration-option","Server","Windows Linux",,"SqlServer","[11.0,)",,,
-"NtfsBlockSizeNotFormatted","definition","TRUE","Low","NTFS block size in volumes with database files <> 64KB","Set allocation unit size on volume '@{volume_mount_point}' to 64 KB. Current size is @{Output.BlockSize} bytes","DefaultRuleset, Performance, Configuration, NTFS","A drive can be formatted with different sizes ranging from 512 bytes to 64K sizes with the default being 4KB (4096 bytes). This setting is also called as “Bytes Per Cluster”. The atomic unit of storage in SQL Server is a page which is 8KB in size. Extents are groups of eight 8 KB pages that are physically contiguous to each other for a total of 64 KB. SQL Server uses extents to store data. Hence, on a SQL Server machine the NTFS Allocation unit size hosting SQL database files (Including tempdb files) should be 64 KB.","https://docs.microsoft.com/archive/blogs/docast/operating-system-best-practice-configurations-for-sql-server","Server","Windows",,"SqlServer","[11.0,)",,,
+"NtfsBlockSizeNotFormatted","definition","TRUE","Low","NTFS block size in volumes with database files <> 64KB","Set allocation unit size on volume @{volume_mount_point} to 64 KB. Current size is @{Output.BlockSize} bytes","DefaultRuleset, Performance, Configuration, NTFS","A drive can be formatted with different sizes ranging from 512 bytes to 64 KB sizes with the default being 4 KB (4096 bytes). This setting is also called as “Bytes Per Cluster”. The atomic unit of storage in SQL Server is a page which is 8KB in size. Extents are groups of eight 8 KB pages that are physically contiguous to each other for a total of 64 KB. SQL Server uses extents to store data. Hence, on a SQL Server machine the NTFS Allocation unit size hosting SQL database files (Including tempdb files) should be 64 KB.","https://docs.microsoft.com/archive/blogs/docast/operating-system-best-practice-configurations-for-sql-server","Server","Windows",,"SqlServer","[11.0,)",,,
 "NtfsBlockSizeNotFormatted","override","TRUE","Medium",,,"",,,,,"AzureVm",,,,,
 "OlapSvcAccSame","definition","TRUE","Low","'Analysis Services' and 'SQL Server Database Engine' use same account","Use different accounts for the 'Analysis Services' service and the 'SQL Server Database Engine' service. Now both services use '@{attr::service::MSOLAP.account}' account","DefaultRuleset, Configuration","Running the 'Analysis Services' service under the same account as the 'SQL Server Database Engine' service is not recommended.","https://docs.microsoft.com/sql/database-engine/configure-windows/configure-windows-service-accounts-and-permissions","Server","Windows",,"SqlServer","[11.0,)",,,
 "OlapSvcStoped","definition","TRUE","Low","'Analysis Services' service is stopped","Run 'Analysis Services' service","DefaultRuleset, Configuration","The 'Analysis Services' service provides online analytical processing (OLAP) and data mining functionality for business intelligence applications.","https://docs.microsoft.com/sql/database-engine/configure-windows/manage-the-database-engine-services","Server","Windows",,"SqlServer","[11.0,)",,,
@@ -224,7 +224,7 @@
 "SqlSvcAccNotSupported","definition","TRUE","Low","'SQL Server Database Engine' service uses not supported account","Use another account to run 'SQL Server Database Engine' service. Current account '@{attr::service::MSSQL.account}' is not supported","DefaultRuleset, Configuration","Running the 'SQL Server Database Engine' service under 'NT AUTHORITY\LOCALSERVICE', 'NT AUTHORITY\SYSTEM' or 'NT AUTHORITY\NETWORKSERVICE' accounts is not supported.","https://docs.microsoft.com/sql/database-engine/configure-windows/configure-windows-service-accounts-and-permissions","Server","Windows",,"SqlServer","[11.0,)",,,
 "ThreadExhaustionCPUBound","definition","TRUE","Low","Worker thread exhaustion on CPU-bound system","Possible worker thread exhaustion (schedulers work queue count is '@{schedulers_work_queue_count}'). Overall runnable tasks count is '@{overall_runnable_tasks_count}' (> 2), indicating the server might be CPU-bound. Configured workers is '@{max_workers_count}'","DefaultRuleset, Performance","Consider overall runnable tasks count and schedulers work queue count.","https://docs.microsoft.com/sql/database-engine/configure-windows/configure-the-max-worker-threads-server-configuration-option","Server","Windows Linux",,"SqlServer","[11.0,)",,,
 "ThreadExhaustionNotCPUBound","definition","TRUE","Low","Possible worker thread exhaustion on non-CPU-bound system","Possible worker thread exhaustion (schedulers work queue count is '@{schedulers_work_queue_count}'). Because overall runnable tasks count is '@{overall_runnable_tasks_count}' (<= 2), indicating the server might not be CPU bound, there might be room to increase max_worker_threads (configured workers is '@{max_workers_count}')","DefaultRuleset, Performance","Consider overall runnable tasks count and schedulers work queue count.","https://docs.microsoft.com/sql/database-engine/configure-windows/configure-the-max-worker-threads-server-configuration-option","Server","Windows Linux",,"SqlServer","[11.0,)",,,
-"ThresholdForParallelism","definition","TRUE","Medium","Option 'cost threshold for parallelism' set to default","Set 'cost threshold for parallelism' option to @{default_cost_parallel}. Current value is @{cost_threshold_for_parallelism}","DefaultRuleset, Configuration, Performance","The 'cost threshold for parallelism' option specifies the threshold at which SQL Server creates and runs parallel plans for queries. SQL Server creates and runs a parallel plan for a query only when the estimated cost to run a serial plan for the same query is higher than the value set in the cost threshold for parallelism. The cost refers to an estimated cost required to run the serial plan on a specific hardware configuration and is not a unit of time. The 'cost threshold for parallelism' option can be set to any value from 0 through 32767. The default value is 5.","https://docs.microsoft.com/sql/database-engine/configure-windows/configure-the-cost-threshold-for-parallelism-server-configuration-option","Server","Windows Linux",,"SqlServer","[11.0,)",,,
+"ThresholdForParallelism","definition","TRUE","Information","Non-default value for 'cost threshold for parallelism' option","Review non-default value @{cost_threshold_for_parallelism} for the 'cost threshold for parallelism' option","DefaultRuleset, Configuration, Performance","The 'cost threshold for parallelism' option specifies the threshold at which SQL Server creates and runs parallel plans for queries. SQL Server creates and runs a parallel plan for a query only when the estimated cost to run a serial plan for the same query is higher than the value set in the cost threshold for parallelism. The cost refers to an estimated cost required to run the serial plan on a specific hardware configuration and is not a unit of time. The 'cost threshold for parallelism' option can be set to any value from 0 through 32767. The default value is 5.","https://docs.microsoft.com/sql/database-engine/configure-windows/configure-the-cost-threshold-for-parallelism-server-configuration-option","Server","Windows Linux",,"SqlServer","[11.0,)",,,
 "WorkerThreadsLargeX64","definition","TRUE","Low","Option 'max worker threads' set to recommended value on x64 system","Reconfigure 'max worker threads' option parameter. Current value (@{max_worker_threads}) is higher than recommended for x64 system (@{recommended_max_worker_threads})","DefaultRuleset, Configuration, Performance, CPU","The max worker threads option configures the number of worker threads that are available to SQL Server processes. The default value for max worker threads is 0. This enables SQL Server to automatically configure the number of worker threads at startup.","https://docs.microsoft.com/sql/database-engine/configure-windows/configure-the-max-worker-threads-server-configuration-option","Server","Windows",,"SqlServer","[11.0,)",,,
 "WorkerThreadsLargeX86","definition","TRUE","Low","Option 'max worker threads' set to recommended value on x86 system","Reconfigure 'max worker threads' option. Current value (@{max_worker_threads}) is higher than recommended for x86 system (@{recommended_max_worker_threads})","DefaultRuleset, Configuration, Performance, CPU","The max worker threads option configures the number of worker threads that are available to SQL Server processes. The default value for max worker threads is 0. This enables SQL Server to automatically configure the number of worker threads at startup.","https://docs.microsoft.com/sql/database-engine/configure-windows/configure-the-max-worker-threads-server-configuration-option","Server","Windows",,"SqlServer","[11.0,)",,,
 "XpCmdShellOn","definition","TRUE","Low","Option 'xp_cmdshell' is disabled","Disable 'xp_cmdshell' as it exposes to security risks","DefaultRuleset, Configuration","The xp_cmdshell option is a SQL Server configuration option that enables system administrators to control whether the xp_cmdshell extended stored procedure can be executed on a system. By default, the xp_cmdshell option is disabled on new installations. ","https://docs.microsoft.com/sql/database-engine/configure-windows/xp-cmdshell-server-configuration-option","Server","Windows Linux",,"SqlServer","[11.0,)",,,
@@ -234,6 +234,7 @@
 "Affinity64Mask","definition","TRUE","Low","Non-default value for 'affinity64 mask' option","Review non-default value @{affinity64_mask} for the 'affinity64 mask' option as it will be removed in a future version","DefaultRuleset, Performance, Configuration","The 'affinity64 mask' binds processors to specific threads, similar to the 'affinity mask' option. Use 'affinity mask' to bind the first 32 processors, and use 'affinity64 mask' to bind the remaining processors.","https://docs.microsoft.com/sql/database-engine/configure-windows/affinity64-mask-server-configuration-option","Server","Windows Linux",,"SqlServer","[11.0,)",,,
 "AffinityIOMask","definition","TRUE","Information","Non-default value for 'affinity I/O mask' option","Review non-default value @{affinity_io_mask} for the 'affinity I/O mask' option","DefaultRuleset, Performance, Configuration","In a multi-processor system, the 'affinity I/O mask' option binds SQL Server disk I/O to a specified subset of CPUs.","https://docs.microsoft.com/sql/database-engine/configure-windows/affinity-input-output-mask-server-configuration-option","Server","Windows Linux",,"SqlServer","[11.0,)",,,
 "AffinityMask","definition","TRUE","Low","Non-default value for 'affinity mask' option","Review non-default value @{affinity_mask} for the 'affinity64 mask' option as it will be removed in a future version","DefaultRuleset, Performance, Configuration","In a multi-processor system, the 'affinity mask' option is used to assign certain CPUs to an instance of SQL Server. When the 'affinity mask' is at its default value of 0, the instance of SQL Server can use all processors in the system for its threads. Setting the 'affinity mask' to a non-default value, restricts SQL Server to using only the assigned CPUs.","https://docs.microsoft.com/sql/database-engine/configure-windows/affinity-mask-server-configuration-option","Server","Windows Linux",,"SqlServer","[11.0,)",,,
+"AGCount","definition","TRUE","Information","Availability database count","Review the number of availability databases (@{database_id})","DefaultRuleset, Performance","The number of databases and availability groups hosted on a single computer (virtual or physical) depends on the hardware and workload. There is no enforced software boundary. However, having more than 100 databases on a single production computer may lead to performance issues, dependent on the workload of the databases.","https://learn.microsoft.com/sql/database-engine/availability-groups/windows/prereqs-restrictions-recommendations-always-on-availability","Server","Windows Linux",,"SqlServer","[11.0,)",,"100",
 "AGDbDisjoined","definition","TRUE","Low","Availability database joined state","Join database '@{databaseName}' to availability group '@{ag_name}' on secondary replica '@{ag_replica_server}'","DefaultRuleset, AlwaysOn","To add a database to an availability group, the database must be an online, read-write database that exists on the server instance that hosts the primary replica. When you add a database, it joins the availability group as a primary database. No corresponding secondary database exists until backups of the new primary database are restored to the server instance that hosts the secondary replica. The new secondary database is in the RESTORING state until it is joined to the availability group. Joining places the secondary database into the ONLINE state and initiates data synchronization with the corresponding primary database.","https://docs.microsoft.com/sql/database-engine/availability-groups/windows/join-a-secondary-database-to-an-availability-group-sql-server","Server","Windows Linux",,"SqlServer","[11.0,)",,,
 "AGEndpointEncryption","definition","TRUE","Low","Database mirroring endpoint encryption","Configure data encryption on endpoint '@{endpoint_name}'","","By default, a database mirroring endpoint requires encryption of data sent over mirroring connections. In this case, the endpoint can connect only to endpoints that also use encryption. Unless you can guarantee that your network is secure, we recommend that you require encryption for your database mirroring connections.","https://docs.microsoft.com/sql/database-engine/availability-groups/windows/prereqs-restrictions-recommendations-always-on-availability","Server","Windows Linux",,"SqlServer","[11.0,)",,,
 "AgentXPs","definition","TRUE","Information","Option 'Agent XPs' is disabled","Enable 'Agent XPs' option","DefaultRuleset, Configuration","The 'Agent XPs' option enables the SQL Server Agent extended stored procedures. When this option is disabled, the SQL Server Agent node is not available in SQL Server Management Studio Object Explorer.","https://docs.microsoft.com/sql/database-engine/configure-windows/agent-xps-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
@@ -242,73 +243,213 @@
 "AGIsFailoverReady","definition","TRUE","Low","Availability database automatic failover readiness","Database '@{databaseName}' in availability group '@{ag_name}' is not ready for automatic failover. Synchronize database on secondary replica '@{ag_replica_server}'","DefaultRuleset, AlwaysOn","Within the context of an availability group, the primary role and secondary role of availability replicas are typically interchangeable in a process known as failover. During the failover, a qualified secondary replica takes over the primary role, recovers its databases, and brings them online as the new primary databases. An automatic failover causes a qualified secondary replica to automatically transition to the primary role after the primary replica becomes unavailable.","https://docs.microsoft.com/sql/database-engine/availability-groups/windows/failover-and-failover-modes-always-on-availability-groups#AutomaticFailover","Server","Windows Linux",,"SqlServer","[11.0,)",,,
 "AGMultipleDHCPListenerSubnets","definition","TRUE","Low","Availability group listener network mode","Reconfigure '@{dns_name}' listener for '@{ag_name}' availability group. Use static IP addresses across multiple subnets","","DHCP network mode is limited to a single subnet that is used for every server instances that hosts a replica in the availability group. To create an availability group across multiple subnets, each subnet requires a static IP address in the listener configuration.","https://docs.microsoft.com/sql/database-engine/availability-groups/windows/create-or-configure-an-availability-group-listener-sql-server","Server","Windows Linux",,"SqlServer","[11.0,)",,,
 "AGReplicasDisconnected","definition","TRUE","Low","Availability replica connection state","Resolve connection issue on availability replica '@{ag_replica_server}' in availability group '@{ag_name}'","DefaultRuleset, AlwaysOn","An availability group supports a replicated environment for a discrete set of user databases, known as availability databases. Each set of availability databases is hosted by an availability replica. Two types of availability replicas exist: a single primary replica, which hosts the primary databases, and one to eight secondary replicas, each of which hosts a set of secondary databases and serves as potential failover targets for the availability group. The primary replica sends transaction log records of each primary database to every secondary database. This process - known as data synchronization - occurs at the database level. Every secondary replica caches the transaction log records and then applies them to its corresponding secondary database.","https://docs.microsoft.com/sql/database-engine/availability-groups/windows/overview-of-always-on-availability-groups-sql-server","Server","Windows Linux",,"SqlServer","[11.0,)",,,
+"AGReplicasRecoveryHealth","definition","TRUE","Low","Availability replica recovery health","Resolve recovery health state on availability replica '@{ag_replica_server}' in availability group '@{ag_name}'","DefaultRuleset, AlwaysOn","An availability group supports a replicated environment for a discrete set of user databases, known as availability databases. Each set of availability databases is hosted by an availability replica. Two types of availability replicas exist: a single primary replica, which hosts the primary databases, and one to eight secondary replicas, each of which hosts a set of secondary databases and serves as potential failover targets for the availability group. The primary replica sends transaction log records of each primary database to every secondary database. This process - known as data synchronization - occurs at the database level. Every secondary replica caches the transaction log records and then applies them to its corresponding secondary database.","https://docs.microsoft.com/sql/database-engine/availability-groups/windows/overview-of-always-on-availability-groups-sql-server","Server","Windows Linux",,"SqlServer","[11.0,)",,,
 "AGReplicasSynchronized","definition","TRUE","Low","Availablity replica synchronization health","Resolve synchronization issues on availability replica '@{ag_replica_server}' in availability group '@{ag_name}'","DefaultRuleset, AlwaysOn","An availability group supports a replicated environment for a discrete set of user databases, known as availability databases. Each set of availability databases is hosted by an availability replica. Two types of availability replicas exist: a single primary replica, which hosts the primary databases, and one to eight secondary replicas, each of which hosts a set of secondary databases and serves as potential failover targets for the availability group. The primary replica sends transaction log records of each primary database to every secondary database. This process - known as data synchronization - occurs at the database level. Every secondary replica caches the transaction log records and then applies them to its corresponding secondary database.","https://docs.microsoft.com/sql/database-engine/availability-groups/windows/overview-of-always-on-availability-groups-sql-server","Server","Windows Linux",,"SqlServer","[11.0,)",,,
 "AGTotalNumber","definition","TRUE","Low","Maximum number of Availability Groups","Review the number of Availability Groups (@{ag_id}) currently hosted on the SQL Server instance","DefaultRuleset, AlwaysOn","The actual number of databases and availability groups you can put on a computer (VM or physical) depends on the hardware and workload, but there is no enforced limit. Microsoft has tested up to 10 AGs and 100 DBs per physical machine. Signs of overloaded systems can include, but are not limited to, worker thread exhaustion, slow response times for availability group system views and DMVs, and/or stalled dispatcher system dumps.","https://docs.microsoft.com/sql/database-engine/availability-groups/windows/prereqs-restrictions-recommendations-always-on-availability#PrerequisitesForAGs","Server","Windows Linux",,"SqlServer","[11.0,)",,"10",
 "AllowUpdates","definition","TRUE","Low","Non-default value for 'allow updates' option","Review non-default value @{allow_updates} for the 'allow updates' option as it has no effect and will be removed in a future version","DefaultRuleset, Performance, Configuration","The 'allow updates' option has no effect and will be removed in a future version of Microsoft SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use this feature.","https://docs.microsoft.com/sql/database-engine/configure-windows/allow-updates-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
 "AutoStartProcs","definition","TRUE","Low","Automated execution of stored procedures is enabled","Disable automated execution of stored procedures: @{sp_name}","DefaultRuleset, Configuration, Security, Performance","Automated execution of stored procedures during the SQL Server startup may delay the availability of the SQL Server instance during the startup procedure. It also introduces the risk of execution of unauthorized code.","https://docs.microsoft.com/sql/relational-databases/stored-procedures/execute-a-stored-procedure#execute-stored-procedures-automatically","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
 "AutoUpdateStatsAsync","definition","TRUE","Information","Option 'AUTO_UPDATE_STATISTICS_ASYNC' is enabled","Disable 'AUTO_UPDATE_STATISTICS_ASYNC' option","DefaultRuleset, Configuration","The Query Optimizer could choose a suboptimal query plan if statistics are out-of-date when the query compiles. User database has AUTO_UPDATE_STATISTICS_ASYNC enabled on one or more user databases. ","https://docs.microsoft.com/sql/t-sql/statements/alter-database-transact-sql-set-options#auto_update_statistics_async","Database","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
-"AzDataDiskCache","definition","TRUE","High","Azure disk caching for data files","Set caching to 'ReadOnly' for disk @{name} (@{volume_mount_point}) as it is used for storing data files. Current setting: '@{caching}'","DefaultRuleset, Performance, DBFileConfiguration, DBConfiguration","Uncached IOPS and throughput plus Cached IOPS and throughput will yield the total possible performance available from the virtual machine within the VMs limits.","https://docs.microsoft.com/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-storage#data-file-caching-policies","Database","Windows","AzureVm","SqlServer","[11.0,)","NOT: tempdb",,
+"AzDataDiskCache","definition","TRUE","High","Azure disk caching for data files","Set caching to 'ReadOnly' for disk '@{name}' (volume @{volume_mount_point}; LUN @{lun}) as it is used for storing data files. Current setting: '@{caching}'","DefaultRuleset, Performance, DBFileConfiguration, DBConfiguration","Uncached IOPS and throughput plus Cached IOPS and throughput will yield the total possible performance available from the virtual machine within the VMs limits.","https://docs.microsoft.com/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-storage#data-file-caching-policies","Database","Windows","AzureVm","SqlServer","[11.0,)","NOT: tempdb",,
 "AzDataDiskStriping","definition","TRUE","Information","Azure data disk striping","Consider using data disk striping to increase I/O bandwidth of volume @{volume_mount_point}","DefaultRuleset, Configuration, Performance","There are throughput and bandwidth limits at the data disk level. Applications that consume resources beyond these limits will be throttled. For more throughput and bandwidth, you can add additional data disks and use disk striping. You can use Storage Spaces inside a virtual machine to combine multiple data disks, creating more storage capacity or performance than is available from a single data disk.","https://docs.microsoft.com/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-storage#disk-striping","Server","Windows","AzureVm","SqlServer","[11.0,)",,,
 "AzDataOnDataDisks","definition","TRUE","Medium","Data files on Azure data disks","Move data files from @{volume_mount_point} to Premium SSD data disk(s)","DefaultRuleset, DBFileConfiguration, DBConfiguration","Azure data disks can be configured for optimal data security and performance. ","https://docs.microsoft.com/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-checklist","Database","Windows","AzureVm","SqlServer","[11.0,)","NOT: tempdb",,
 "AzDataOnDataDisks","override","TRUE","Low",,,"",,,,,,,,"master model msdb",,
 "AzDbDefaultLocation","definition","TRUE","Medium","Database default locations","Configure default @{setting_name} file location","DefaultRuleset, Configuration, Performance","Default database file location setting makes new data and transaction log files placed on drives configured for this specific workload.","https://docs.microsoft.com/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-checklist","Server","Windows","AzureVm","SqlServer","[11.0,)",,,
 "AzDiskColumnCount","definition","TRUE","Medium","Storage spaces disk column count","Use all @{poolDiskCount} physical disks available in your storage pool for virtual disk (@{volume_mount_point}), currently used: @{columnCount} physical disk(s)","DefaultRuleset, DBFileConfiguration, DBConfiguration, Performance","Increasing virtual disk column count improves the disk's performance. The number of disks in the pool is the maximum available number of columns.","https://docs.microsoft.com/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-checklist","Server","Windows","AzureVm","SqlServer","[11.0,)",,,
 "AzErrorLogLocation","definition","TRUE","Medium","Error log and default trace files on Azure data disk","Move error log and default trace files to data disk","DefaultRuleset, Configuration, Performance","Storing error log and default trace files on data disk improves performance.","https://docs.microsoft.com/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-checklist","Server","Windows","AzureVm","SqlServer","[11.0,)",,,
-"AzPremSsdDataFiles","definition","TRUE","High","Use premium SSDs for SQL Server data files","Move data files from @{volume_mount_point} to Premium SSD disk","DefaultRuleset, Performance, DBFileConfiguration, DBConfiguration","Standard HDDs and SSDs have varying latencies and bandwidth and are only recommended for dev/test workloads. Production workloads should use premium SSDs.","https://docs.microsoft.com/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-storage","Database","Windows","AzureVm","SqlServer","[11.0,)","NOT: tempDb",,
+"AzPremSsdDataFiles","definition","TRUE","High","Use premium SSDs for SQL Server data files","Move data files from disk '@{name}' (volume @{volume_mount_point}; LUN @{lun}) to Premium SSD disk","DefaultRuleset, Performance, DBFileConfiguration, DBConfiguration","Standard HDDs and SSDs have varying latencies and bandwidth and are only recommended for dev/test workloads. Production workloads should use premium SSDs.","https://docs.microsoft.com/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-storage","Database","Windows","AzureVm","SqlServer","[11.0,)","NOT: tempDb",,
 "AzPremSsdDataFiles","override","TRUE","Low",,,"",,,,,,,,"master model msdb",,
 "AzTempDbFileLocation","definition","TRUE","High","Tempdb files on Azure temp drive","Move tempdb files from @{volume_mount_point} to the local ephemeral SSD (temp disk)","DefaultRuleset, Performance, DBFileConfiguration, DBConfiguration","Storing tempdb files on a local ephemeral SSD improves the performance of workloads that use temporary objects heavily (e.g. queries handling large recordsets, index rebuilds, row versioning isolation levels, temp tables, and triggers).","https://docs.microsoft.com/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-checklist","Database","Windows","AzureVm","SqlServer","[11.0,)","tempdb",,
-"AzTranLogDiskCache","definition","TRUE","High","Azure disk caching for transaction logs","Set caching to 'None' for disk @{name} (@{volume_mount_point}) as it is used for storing transaction log files. Current setting: '@{caching}'","DefaultRuleset, Performance, DBFileConfiguration, DBConfiguration","There is no performance benefit to enabling caching for the Transaction log disk, and in fact having either Read-only or Read/Write caching enabled on the log drive can decrease the amount of cache available for reads on the data drive","https://docs.microsoft.com/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-storage#data-file-caching-policies","Database","Windows","AzureVm","SqlServer","[11.0,)","NOT: tempdb",,
+"AzTranLogDiskCache","definition","TRUE","High","Azure disk caching for transaction logs","Set caching to 'None' for disk '@{name}' (volume @{volume_mount_point}; LUN @{lun}) as it is used for storing transaction log files. Current setting: '@{caching}'","DefaultRuleset, Performance, DBFileConfiguration, DBConfiguration","There is no performance benefit to enabling caching for the Transaction log disk, and in fact having either Read-only or Read/Write caching enabled on the log drive can decrease the amount of cache available for reads on the data drive","https://docs.microsoft.com/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-storage#data-file-caching-policies","Database","Windows","AzureVm","SqlServer","[11.0,)","NOT: tempdb",,
 "BackupCompression","definition","TRUE","Information","Option 'backup compression default' is disabled","Enable 'backup compression default' option","DefaultRuleset, Configuration, Performance, Backup","The 'backup compression default' option determines whether the server instance creates compressed backups by default. Because a compressed backup is smaller than an uncompressed backup of the same data, compressing a backup typically requires less device I/O and therefore usually increases backup speed significantly.","https://docs.microsoft.com/sql/database-engine/configure-windows/view-or-configure-the-backup-compression-default-server-configuration-option","Server","Windows Linux",,"Standard, Enterprise, ManagedInstance","[11.0,)",,,
 "BackupTables","definition","TRUE","Information","Too many rows in backup or restore history tables","Reduce number of rows in table '@{table_name}' to less than @{threshold}","DefaultRuleset, Configuration","The upgrade process of a SQL Server instance may appear to hang if the number of rows in the following backup and restore system tables is very high: 'backupfile', 'backupmediafamily', 'backupmediaset', 'backupset', 'restorefile', 'restorefilegroup', 'restorehistory'. This is due to the fact that it would take longer to modify the backup and restore system tables in MSDB database.","https://docs.microsoft.com/sql/relational-databases/system-stored-procedures/sp-delete-backuphistory-transact-sql","Server","Windows Linux",,"SqlServer","[11.0,)",,"10000",
 "C2AuditMode","definition","TRUE","Information","Non-default value for 'c2 audit mode' option","Review non-default value @{c2_audit_mode} for the 'c2 audit mode' option as it will be removed in a future version","DefaultRuleset, Configuration","When enabled, the 'c2 audit mode' option collects all attempts to access statements and objects. Enabling this option triggers a significant amount of data collection over a short period of time for even moderately active Microsoft SQL Server instances.","https://docs.microsoft.com/sql/database-engine/configure-windows/c2-audit-mode-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
 "CCCompliance","definition","TRUE","Information","Non-default value for 'common criteria compliance enabled' option","Review non-default value @{common_criteria_compliance_enabled} for the 'common criteria compliance enabled' option","DefaultRuleset, Performance, Configuration","SQL Server is being developed to achieve not only the best performance results but also to be the most secure database system ever released. Microsoft has the commitment to be compliant with the most important standards. The most recent SQL Server Editions are getting these recognitions, including the Common Criteria certification. Part of that commitment is the independent third-party evaluation of our products and in using the Common Criteria (CC, ISO15408) as a proven and accepted process to ensure compliance with Common Evaluation Methodologies.","https://docs.microsoft.com/sql/database-engine/configure-windows/common-criteria-compliance-enabled-server-configuration-option","Server","Windows Linux",,"Enterprise, ManagedInstance","[11.0,)",,,
 "ClrEnabled","definition","TRUE","Information","Non-default value for 'clr enabled' option","Review non-default value @{clr_enabled} for the 'clr enabled' option","DefaultRuleset, Configuration","This option determines whether user assemblies and CLR functionality or objects can be used on a Microsoft SQL Server instance. Disable this option if you do not plan to use CLR database objects on the SQL Server instance.","https://docs.microsoft.com/sql/relational-databases/clr-integration/clr-integration-enabling","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ColumnstoreLargePageModel","definition","TRUE","Medium","Columnstore indexes with large page memory model","Disable trace flag 834 when using Columnstore indexes","","Interoperability of Columnstore indexes with large page memory model may cause severe performance issues, access violations, insufficient system memory errors, or a non-yielding Scheduler errors.","https://docs.microsoft.com/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql#tf834","Server","Windows Linux",,"SqlServer","[11.0,)",,,
 "CompareRunConfigured","definition","TRUE","Information","Run and config values are different","Use 'RECONFIGURE' after 'sp_configure' to update run value. Config value is different from run value in: @{unsaved_option}","DefaultRuleset, Performance, Configuration","SQL Server instance configuration settings have two values: a run value which is the currently active value and a config value which is the value that was last configured. Generally, these two values are the same, but if a setting has been changed but the change is not yet applied, confusion can arise for administrators and, in extreme cases, the system can become unstable.","https://docs.microsoft.com/sql/relational-databases/system-catalog-views/sys-configurations-transact-sql","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"CompilationsPerSec","definition","TRUE","Low","High SQL compilations frequency","Investigate the use of stored procedures, database options and server options to reduce the proportion of plan compilations to batch requests per second (@{sql_compilations_sec:0.##} / @{batch_request_sec:0.##})","DefaultRuleset, Performance","SQL Server will try to reuse compiled plans from the plan cache. The reuse of a plan means that a new plan does not need to be optimized and compiled and results in greater efficiency. A high proportion of compilations indicates many ad-hoc queries and will result in inefficiency. Use sp_executesql for dynamic SQL statements. In addition, investigate the possibility of changing prepared SQL and ad-hoc SQL statements to stored procedures. The FORCED PARAMETERIZATION option can be set at the database level. This makes SQL Server become much more aggressive in deciding which queries to auto-parameterize, but can potentially introduce parameter-sensitivity problems (e.g. parameter sniffing).","https://learn.microsoft.com/sql/relational-databases/performance-monitor/sql-server-sql-statistics-object","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,"0.1",
 "ContainedDbAuthentication","definition","TRUE","Information","Non-default value for 'contained database authentication' option","Review non-default value @{contained_database_authentication} for the 'contained database authentication' option","DefaultRuleset, Configuration, Security","When contained databases are enabled, database users other than members of the 'sysadmin' and 'securityadmin' fixed server roles can grant access to the instance of SQL Server.","https://docs.microsoft.com/sql/database-engine/configure-windows/contained-database-authentication-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"CursorRequestsPerSec","definition","TRUE","Low","High cursor requests frequency","Determine if cursors are the most appropriate means to accomplish the processing or whether a set-based operation, which is generally more efficient, is possible, Cursor Requests/sec (@{cursor_requests_sec:0.##}) per Batch requests/sec (@{batch_request_sec:0.##})  is greater than @{threshold:P0}","DefaultRuleset, Performance","Cursor Requests/sec is the number of cursor requests received by SQL Server. More than 20 cursor requests per 100 Batch Requests/sec on an average may indicate that the applications are designed to use cursors extensively instead of set-based operations. Look at the Cursor Requests/sec counter to get a general overview for how many cursors are being used on the system. Systems that have high CPU utilization because of small fetch sizes typically have hundreds of cursor requests per second. Redesign queries and applications to use set-based operations rather than cursors where possible.","https://techcommunity.microsoft.com/t5/sql-server-blog/increase-your-sql-server-performance-by-replacing-cursors-with/ba-p/383359","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,"0.2",
 "CursorThreshold","definition","TRUE","Information","Non-default value for 'cursor threshold' option","Review non-default value @{cursor_threshold} for the 'cursor threshold' option","DefaultRuleset, Performance, Configuration","When cursors generate keysets for a result set, the query optimizer estimates how many rows the keyset will contain. If the number is larger than this threshold, the keyset is generated asynchronously. The default value of -1 results in SQL Server generating all keysets asynchronously. If you set the value too low, overall performance may be impacted because small results sets are better built synchronously.","https://docs.microsoft.com/sql/database-engine/configure-windows/configure-the-cursor-threshold-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
 "DatabaseMailXPs","definition","TRUE","Information","Non-default value for 'Database Mail XPs' option","Review non-default value @{Database_Mail_XPs} for the 'Database Mail XPs' option","DefaultRuleset, Configuration, Security","Configuring the 'Database Mail XPs' option to 1 enables Database Mail on the instance of SQL Server. This configuration is off by default to reduce the attack surface area of SQL Server. Do not enable this functionality unless you intend to use Database Mail.","https://docs.microsoft.com/sql/database-engine/configure-windows/database-mail-xps-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"DbBackupMedia","definition","TRUE","Low","Backup files on a separate physical location","Place backup file @{physical_device_name} on a separate physical location from the database files","DefaultRuleset, Backup, Performance, Configuration, DBConfiguration, DBFileConfiguration","It is recommended that database backups are placed on a separate physical location or device from the database files. When your physical drive that stores your databases malfunctions or crashes, recoverability depends on the ability to access the separate drive or remote device that stored the backups in order to perform a restore. Also, putting the database and backup files on the separate devices optimizes the I/O performance for both the production use of the database and the writing of backups.","https://learn.microsoft.com/sql/relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases#best-practice-recommendations","Database","Windows",,"SqlServer","[11.0,)",,,
 "DbCompression","definition","TRUE","Information","Uncompressed database tables and indexes","Turn on compression for these @{ObjectType}: @{ObjectName}, total space used by these objects: @{TotalSpaceMB:N2} MB","DefaultRuleset, Configuration, Performance","The compression capability at either the row or page level provides an opportunity to save disk space and improve performance, with the tradeoff of requiring a bit more CPU to compress and decompress the data, but requiring less memory and disk access improving performance in many workloads. The data pages are kept compressed when they are uploaded to memory. This check fires if a relatively large amount of space is on indexes without compression (for example, more than 10GB).","https://docs.microsoft.com/sql/relational-databases/sql-server-index-design-guide","Database","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)","NOT: master model msdb tempdb","1280000",
+"DbMirroring","definition","TRUE","Low","Database mirroring","Plan to modify applications that currently use database mirroring as it is deprecated and will be removed in a future version","DefaultRuleset, Configuration, Deprecated","Database mirroring is a solution for increasing the availability of a SQL Server database. Mirroring is implemented on a per-database basis and works only with databases that use the full recovery model. Database mirroring is deprecated and will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use this feature. Use Always On availability groups instead.","https://learn.microsoft.com/sql/database-engine/database-mirroring/database-mirroring-sql-server","Server","Windows",,"SqlServer","[11.0,)",,,
 "DbRecoveryModel","definition","TRUE","Medium","Databases with 'SIMPLE' recovery model","Change recovery model to 'FULL' or 'BULK_LOGGED'","DefaultRuleset, Configuration","A database with the 'SIMPLE' recovery model does not support log backups. As a result, when you need to restore such a database, all the transactions since the last database backup or differential backup will be lost. Review databases that have the 'SIMPLE' recovery model. If the maximum amount of data loss involved is not acceptable, change the recovery model to 'FULL' or 'BULK_LOGGED' and schedule frequent log backups.","https://docs.microsoft.com/sql/relational-databases/backup-restore/recovery-models-sql-server","Database","Windows Linux",,"SqlServer","[11.0,)","NOT: model tempdb msdb master",,
-"DbSpaceAvailable","definition","TRUE","Medium","Low free space in data files","Increase space for data files. Currently @{spaceAvailableRel:P0} is available. Threshold is set to @{threshold:P0}. Total size of data files: @{totalMB:N2} MB. Free space: @{freeMB:N2} MB","DefaultRuleset, Configuration, DBFileConfiguration","Average available space in data files is less than the threshold.","https://docs.microsoft.com/sql/relational-databases/databases/database-states","Database","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,"0.25",
-"DbStandby","definition","TRUE","Information","STANDBY mode is enabled","Disable STANDBY mode for database","DefaultRuleset, Configuration","A Database in STANDBY mode will be online as READ ONLY, WITH RESTORE LOG allowed. If recovery is not complete, then the availability of the database might be affected. Usually log shipped secondary databases are configured to be in STANDBY mode.","https://docs.microsoft.com/sql/t-sql/statements/restore-statements-arguments-transact-sql#with-options","Database","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"DbSpaceAvailable","definition","TRUE","Medium","Low free space in data files","Increase space for data files. Currently @{spaceAvailableRel:P0} is available. Threshold is set to @{threshold:P0}. Total size of data files: @{totalMB:N2} MB. Free space: @{freeMB:N2} MB","DefaultRuleset, Configuration, DBFileConfiguration","Average available space in data files is less than the threshold.","https://docs.microsoft.com/troubleshoot/sql/admin/considerations-autogrow-autoshrink#why-do-i-have-to-worry-about-disk-space-if-size-settings-are-automatically-controlled","Database","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,"0.25",
+"DbStandby","definition","TRUE","Information","STANDBY mode is enabled","Check database availability. A database is in STANDBY mode","DefaultRuleset, Configuration","A database in STANDBY mode will be online as READ ONLY, WITH RESTORE LOG allowed. If recovery is not complete, then the availability of the database might be affected. Usually log shipped secondary databases are configured to be in STANDBY mode.","https://docs.microsoft.com/sql/t-sql/statements/restore-statements-arguments-transact-sql#with-options","Database","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
 "DbState","definition","TRUE","Low","Database with unavailable state","Check '@{DbName}' database availability. Current database state is: @{DbStateDesc}","DefaultRuleset, Configuration","Database unavailability may affect expected application behavior due to the impossibility of establishing user connections. The issue occurs when a database is in any of the following states: 'RECOVERY_PENDING', 'RECOVERING', 'SUSPECT', or 'RESTORING'.","https://docs.microsoft.com/sql/relational-databases/databases/database-states","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"DeadlockFrequency","definition","TRUE","Low","High deadlock frequency","Investigate a high frequency of deadlocked transactions (@{number_of_deadlocks_sec:0.##})","DefaultRuleset, Performance","One or more SQL Server instances report a high frequency of deadlocked transactions. This can result in blocking, reduced concurrency, and degraded performance. Get more details on the processes that are causing deadlock between each other. To view deadlock information, the Database Engine provides monitoring tools in the form of Extended Event Sessions with the Deadlock Graph event or the trace flags 1204 or 1222 which writes more detailed information to the SQL Server Error log. Once you have identified the problematic queries you need to optimize the code, indexes, order of operations and isolation level used and required by the process.","https://learn.microsoft.com/sql/relational-databases/sql-server-transaction-locking-and-row-versioning-guide?#deadlocks","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
 "DisallowResultsTriggers","definition","TRUE","Information","Option 'disallow results from triggers' is disabled","Enable 'disallow results from triggers' option as the ability to return result sets from triggers will be removed in a future version","DefaultRuleset, Configuration","Use the 'disallow results from triggers' option to control whether triggers return result sets. Triggers that return result sets may cause unexpected behavior in applications that are not designed to work with them.","https://docs.microsoft.com/sql/database-engine/configure-windows/disallow-results-from-triggers-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"DomainController","definition","TRUE","Medium","SQL Server on a domain controller","SQL Server is installed on a domain controller. Consider migrating SQL Server to a dedicated machine","DefaultRuleset, Configuration, Security","For security reasons, it is strongly not recommend installing SQL Server on a domain controller.","https://learn.microsoft.com/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server#DC_support","Server","Windows",,"SqlServer","[11.0,)",,,
 "EKMProvider","definition","TRUE","Information","Non-default value for 'EKM provider enabled' option","Review non-default value @{EKM_provider_enabled} for the 'EKM provider enabled' option","DefaultRuleset, Configuration","The 'EKM provider enabled' option controls Extensible Key Management device support in SQL Server. SQL Server provides data encryption capabilities together with Extensible Key Management (EKM), using the Microsoft Cryptographic API (MSCAPI) provider for encryption and key generation. Encryption keys for data and key encryption are created in transient key containers, and they must be exported from a provider before they are stored in the database. This approach enables key management that includes an encryption key hierarchy and key backup, to be handled by SQL Server.","https://docs.microsoft.com/sql/database-engine/configure-windows/ekm-provider-enabled-server-configuration-option","Server","Windows Linux",,"Standard, Enterprise, ManagedInstance","[11.0,)",,,
 "EKMProvider","override","False","Low",,,"",,,,,,"Standard","[11.0, 15.0)",,,
+"ErrorLog109","definition","TRUE","Medium","Database engine error 109","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","There are more columns in the INSERT statement than values specified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog211","definition","TRUE","High","Database engine error 211","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","Possible schema corruption.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog232","definition","TRUE","Information","Database engine error 232","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","Arithmetic overflow error.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog566","definition","TRUE","Medium","Database engine error 566","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","An error occurred while writing an audit trace.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog602","definition","TRUE","Information","Database engine error 602","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","Could not find an entry for table or index. This error can occur if a stored procedure references a dropped table, or metadata is corrupted.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog603","definition","TRUE","Information","Database engine error 603","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","Could not find an entry for table or index. This error can occur if a stored procedure references a dropped table, or metadata is corrupted.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog605","definition","TRUE","Medium","Database engine error 605","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","Attempt to fetch a logical page failed. This error generally signifies page or allocation corruption, and often is caused by hardware or disk device driver failure.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-605-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog608","definition","TRUE","Medium","Database engine error 608","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","No catalog entry found for partition. The metadata is inconsistent.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog701","definition","TRUE","Information","Database engine error 701","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","There is insufficient system memory in resource pool to run this query. Insufficient memory can be caused by a number of factors that include operating system settings, physical memory availability, other components use memory inside SQL Server, or memory limits on the current workload.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-701-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog802","definition","TRUE","Medium","Database engine error 802","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","There is insufficient memory available in the buffer pool. This is caused when the buffer pool is full and the buffer pool cannot grow any larger.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-802-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog823","definition","TRUE","Medium","Database engine error 823","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","The operating system returned error to SQL Server. This error usually indicates that there is a problem with underlying storage system or the hardware or a driver that is in the path of the I/O request.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-823-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog824","definition","TRUE","Medium","Database engine error 824","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","SQL Server detected a logical consistency-based I/O error. This error usually indicates that there is a problem with underlying storage system or the hardware or a driver that is in the path of the I/O request.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-824-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog825","definition","TRUE","Medium","Database engine error 825","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A read of a file succeeded after failing one or more times. This error indicates that the read operation had to be reissued at least one time, and indicates a major problem with the disk hardware.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-825-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog829","definition","TRUE","High","Database engine error 829","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A page is marked as RestorePending, which may indicate disk corruption. To recover from this state, perform a restore.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog832","definition","TRUE","Medium","Database engine error 832","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A page that should have been constant has changed. This usually indicates a memory failure or other hardware or operating system corruption. An external factor has caused a database page to be modified outside the normal SQL Server engine code used to change database pages.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-832-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog833","definition","TRUE","Information","Database engine error 833","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","SQL Server has encountered occurrences of I/O requests taking a long time to complete. This error indicates a problem with the I/O subsystem. This problem can be caused by operating system performance issues, hardware errors, firmware errors, device driver problems, or filter driver intervention in the I/O process or storage path of database files.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-833-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog844","definition","TRUE","Information","Database engine error 844","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A timeout occurred while waiting for buffer latch. A process is waiting to acquire a latch. This can occur if an I/O operation taking too long to complete.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-844-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog845","definition","TRUE","Information","Database engine error 845","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A timeout occurred while waiting for buffer latch. A process was waiting to acquire a latch, but the process waited until the time limit expired and failed to acquire one. This can occur if an I/O operation takes too long to complete.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-845-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog846","definition","TRUE","Information","Database engine error 846","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A timeout occurred while waiting for buffer latch. Not continuing to wait. A computer might stop responding, or a timeout or some other disruption of regular operations might occur at the same time that SQL Server writes buffer latch errors to the SQL Server error log.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-846-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog847","definition","TRUE","Information","Database engine error 847","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A timeout occurred while waiting for buffer latch. Continuing to wait. A computer might stop responding, or a timeout or some other disruption of regular operations might occur at the same time that SQL Server writes buffer latch errors to the SQL Server error log.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-847-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog905","definition","TRUE","Information","Database engine error 905","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A database cannot be started because it contains one or more partitioned tables or indexes. This edition of SQL Server cannot use table and index partitioning.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-905-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog909","definition","TRUE","Information","Database engine error 909","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A database cannot be started because it contains one or more objects enabled with data compression or vardecimal storage format. This edition of SQL Server cannot use data compression and vardecimal storage format.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog933","definition","TRUE","Information","Database engine error 933","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A database cannot be started because some of the database functionality is not available in this edition of SQL Server.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog934","definition","TRUE","Information","Database engine error 934","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","SQL Server cannot load a database because Change Data Capture is enabled. This edition of SQL Server does not support Change Data Capture.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog945","definition","TRUE","Medium","Database engine error 945","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A database cannot be opened due to inaccessible files or insufficient memory or disk space.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-945-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog1101","definition","TRUE","Medium","Database engine error 1101","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","Could not allocate a new page because of insufficient disk space.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-1101-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog1105","definition","TRUE","Medium","Database engine error 1105","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","Could not allocate space for an object because a filegroup is full.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-1105-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog1205","definition","TRUE","Information","Database engine error 1205","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","Transaction was deadlocked on a resources with another process and has been chosen as the deadlock victim. This error indicates that resources are accessed in conflicting order on separate transactions, causing a deadlock.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-1205-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog1450","definition","TRUE","Medium","Database engine error 1450","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","The ALTER DATABASE command failed because the worker thread cannot be created.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog2570","definition","TRUE","Medium","Database engine error 2570","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A column value is outside the range of possible values for the column data type.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-2570-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog3041","definition","TRUE","Medium","Database engine error 3041","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","BACKUP failed to complete a command.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog3043","definition","TRUE","Medium","Database engine error 3043","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","BACKUP detected an error on page.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog3197","definition","TRUE","Information","Database engine error 3197","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","I/O is frozen on a database.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog3260","definition","TRUE","Information","Database engine error 3260","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","An internal buffer has become full. The server is out of memory.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-3260-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog3266","definition","TRUE","Information","Database engine error 3266","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A backup data is incorrectly formatted. Backup sets on the media might be damaged and unusable.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog3271","definition","TRUE","Information","Database engine error 3271","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A nonrecoverable I/O error occurred. This is a general error that occurs when the operating system raises an error while performing I/O during a backup or restore operation.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-3271-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog3313","definition","TRUE","Medium","Database engine error 3313","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","During redoing of a logged operation, an error occurred.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-3313-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog3314","definition","TRUE","Medium","Database engine error 3314","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","During undoing of a logged operation, an error occurred.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-3314-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog3316","definition","TRUE","Information","Database engine error 3316","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","During undo of a logged operation, an error occurred. The row was not found.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog3409","definition","TRUE","Medium","Database engine error 3409","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","Performance counter shared memory setup failed.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog3414","definition","TRUE","Medium","Database engine error 3414","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","An error occurred during recovery, preventing a database from restarting.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-3414-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog3417","definition","TRUE","Medium","Database engine error 3417","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","Cannot recover the master database. SQL Server is unable to run.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-3417-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog3420","definition","TRUE","Information","Database engine error 3420","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A database snapshot has failed an IO operation and is marked suspect.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog3431","definition","TRUE","Medium","Database engine error 3431","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","Could not recover a database because of unresolved transaction outcomes.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-3431-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog3437","definition","TRUE","Medium","Database engine error 3437","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","An error occurred while recovering a database. Unable to connect to Distributed Transaction Coordinator to check the completion status of a transaction.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-3437-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog3452","definition","TRUE","Information","Database engine error 3452","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","Recovery of a database detected possible identity value inconsistency in a table.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-3452-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog3456","definition","TRUE","Medium","Database engine error 3456","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","Could not redo log record.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-3456-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog3619","definition","TRUE","Medium","Database engine error 3619","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","Could not write a checkpoint record because the log is out of space. The transaction log is out of disk space.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-3619-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog3859","definition","TRUE","Medium","Database engine error 3859","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","The system catalog was updated directly. This error indicates a user initiated changes to system tables. Manually updating system tables is not supported.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-3859-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog5105","definition","TRUE","Medium","Database engine error 5105","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A file activation error occurred. The physical file name may be incorrect.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog5180","definition","TRUE","Medium","Database engine error 5180","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","Could not open File Control Bank for invalid file. A query or operation may fail when an invalid file ID is referenced.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-5180-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog5243","definition","TRUE","Information","Database engine error 5243","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","An inconsistency was detected during an internal operation. SQL Server detected a structural inconsistency in an in-memory storage engine structure.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-5243-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog7105","definition","TRUE","Information","Database engine error 7105","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A large object data referenced by a database page row cannot be accessed. This is usually caused by transactions that can read uncommitted data on a data page.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-7105-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog7359","definition","TRUE","Information","Database engine error 7359","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","The OLE DB provider for a linked server reported a change in schema version between compile time and run time.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog8621","definition","TRUE","Medium","Database engine error 8621","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","The query processor ran out of stack space during query optimization. The size of the expanded query is the most likely cause of the error.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-8621-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog8628","definition","TRUE","Medium","Database engine error 8628","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A timeout occurred while waiting to optimize the query.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog8642","definition","TRUE","Medium","Database engine error 8642","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","The query processor could not start the necessary thread resources for parallel query execution.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-8642-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog8645","definition","TRUE","Information","Database engine error 8645","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A timeout occurred while waiting for memory resources to execute the query.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-8645-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog8909","definition","TRUE","Medium","Database engine error 8909","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A page contains an incorrect page ID in its page header.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog8966","definition","TRUE","Information","Database engine error 8966","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","Unable to read and latch page.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-8966-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog9002","definition","TRUE","Medium","Database engine error 9002","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A database transaction log is full.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-9002-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog9004","definition","TRUE","High","Database engine error 9004","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","An error was encountered while processing the log during rollback, recovery, or replication. This could indicate an error detected by the operating system or an internal consistency error detected by SQL Server.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-9004-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog9642","definition","TRUE","Information","Database engine error 9642","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","An error occurred in a Service Broker/Database Mirroring transport connection endpoint.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog9691","definition","TRUE","Medium","Database engine error 9691","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","An endpoint has stopped listening for connections.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog9692","definition","TRUE","Information","Database engine error 9692","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","An endpoint cannot listen on a port because it is in use by another process.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-9692-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog9693","definition","TRUE","Information","Database engine error 9693","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","An endpoint cannot listen for connections due to an error.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog17065","definition","TRUE","Medium","Database engine error 17065","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","This error can be caused by transient, timing-related errors, or by in-memory or on-disk data corruption.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-17065-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog17066","definition","TRUE","Medium","Database engine error 17066","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","This error can be caused by transient, timing-related errors, or by in-memory or on-disk data corruption.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-17066-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog17067","definition","TRUE","Medium","Database engine error 17067","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","This error can be caused by transient, timing-related errors, or by in-memory or on-disk data corruption.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-17067-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog17194","definition","TRUE","Medium","Database engine error 17194","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","This error indicates that the client has closed the connection. This error could occur because the connection timeout has expired.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-17194-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog17204","definition","TRUE","Information","Database engine error 17204","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","Could not open a file. SQL Server was unable to open the file because of the operating system error.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-17204-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog17207","definition","TRUE","Information","Database engine error 17207","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","An operating system error occurred while creating or opening a file. SQL Server was unable to open the file because of the operating system error.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-17207-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog17659","definition","TRUE","High","Database engine error 17659","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A system table has been updated directly and cache coherence may not have been maintained. This error indicates a user initiated changes to system tables. Manually updating system tables is not supported.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-17659-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog17806","definition","TRUE","Medium","Database engine error 17806","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","Security Support Provider Interface handshake failed while establishing a connection with integrated security.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog17832","definition","TRUE","Information","Database engine error 17832","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","The login packet used to open the connection is structurally invalid. This error could occur because the packet was created improperly or because the packet was damaged during transmission.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-17832-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog17884","definition","TRUE","Medium","Database engine error 17884","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","New queries assigned to process have not been picked up by a worker thread.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-17884-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog17887","definition","TRUE","Medium","Database engine error 17887","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","An IO Completion Listener appears to be non-yielding. This error indicates that there is a possible problem with the I/O Completion Port Listener when executing the I/O Completion routine for a network read/write event.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-17887-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog17888","definition","TRUE","Medium","Database engine error 17888","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","All schedulers on a node appear deadlocked due to a large number of waiting worker threads.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog17890","definition","TRUE","Medium","Database engine error 17890","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A significant part of SQL Server process memory has been paged out. This may result in a performance degradation.","https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-17890-database-engine-error","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog18056","definition","TRUE","Information","Database engine error 18056","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","The client was unable to reuse a session, which had been reset for connection pooling. This error may have been caused by an earlier operation failing.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog18204","definition","TRUE","High","Database engine error 18204","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A backup device failed because of the operating system error.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog18272","definition","TRUE","Information","Database engine error 18272","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","During restore restart, an I/O error occurred on a checkpoint file.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog19034","definition","TRUE","Medium","Database engine error 19034","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","Cannot start C2 audit trace.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog26023","definition","TRUE","Medium","Database engine error 26023","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","SQL Server TCP provider failed to listen on a port. TCP port is already in use.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog26024","definition","TRUE","Medium","Database engine error 26024","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","SQL Server TCP provider failed to listen on a port.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog26037","definition","TRUE","Medium","Database engine error 26037","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","SQL Server Network Interface library could not register the Service Principal Name (SPN) for SQL Server service. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog26038","definition","TRUE","Medium","Database engine error 26038","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","SQL Server Network Interface library could not register the Service Principal Name (SPN) for SQL Server service. This SPN should be deregistered manually to avoid client authentication errors.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog28034","definition","TRUE","Information","Database engine error 28034","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","Connection handshake failed. A login does not have CONNECT permission on the endpoint.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog28036","definition","TRUE","Medium","Database engine error 28036","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","Connection handshake failed. The certificate used by the endpoint was not found.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog28047","definition","TRUE","Information","Database engine error 28047","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A login attempt failed with error.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog28048","definition","TRUE","Information","Database engine error 28048","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A login attempt by an user failed with error.","https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog35201","definition","TRUE","Information","Database engine error 35201","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A connection timeout has occurred while attempting to establish a connection to an availability replica. Either a networking or firewall issue exists, or the endpoint address provided for the replica is not the database mirroring endpoint.","https://docs.microsoft.com/sql/database-engine/availability-groups/windows/troubleshoot-always-on-availability-groups-configuration-sql-server","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog35204","definition","TRUE","Information","Database engine error 35204","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","The connection between server instances has been disabled because the database mirroring endpoint was either disabled or stopped.","https://docs.microsoft.com/sql/database-engine/availability-groups/windows/troubleshoot-always-on-availability-groups-configuration-sql-server","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog35206","definition","TRUE","Information","Database engine error 35206","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A connection timeout has occurred on a previously established connection to an availability replica. Either a networking or a firewall issue exists or the availability replica has transitioned to the resolving role.","https://docs.microsoft.com/sql/database-engine/availability-groups/windows/troubleshoot-always-on-availability-groups-configuration-sql-server","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog35207","definition","TRUE","Information","Database engine error 35207","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","Connection attempt on an availability group failed because of error.","https://docs.microsoft.com/sql/database-engine/availability-groups/windows/troubleshoot-always-on-availability-groups-configuration-sql-server","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog35217","definition","TRUE","Medium","Database engine error 35217","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","The thread pool for AlwaysOn Availability Groups was unable to start a new worker thread because there are not enough available worker threads.","https://docs.microsoft.com/sql/database-engine/availability-groups/windows/troubleshoot-always-on-availability-groups-configuration-sql-server","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog41142","definition","TRUE","Medium","Database engine error 41142","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","The availability replica for an availability group cannot become the primary replica. One or more databases are not synchronized or have not joined the availability group.","https://docs.microsoft.com/sql/database-engine/availability-groups/windows/troubleshoot-always-on-availability-groups-configuration-sql-server","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLog41144","definition","TRUE","Medium","Database engine error 41144","Database engine error @{error} occurred @{error_count} times in the last @{history_days} days. Last occurrence at @{last_occurrence}.","","A local availability replica is in a failed state. The replica failed to read or update the persisted configuration data.","https://docs.microsoft.com/sql/database-engine/availability-groups/windows/troubleshoot-always-on-availability-groups-configuration-sql-server","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ErrorLogAge","definition","TRUE","Low","Error log retention settings","Revise error log retention settings. Error log contains less than @{threshold} days of history","DefaultRuleset, Configuration","The SQL Server error log contains lots of information that is generated by the SQL Server. The error log file is initialized every time that the instance of SQL Server is started. Specify the maximum number of archived error log files created before they are recycled. The default is 6, not including the current one.","https://learn.microsoft.com/troubleshoot/sql/admin/manage-error-log","Server","Windows Linux",,"SqlServer","[11.0,)",,"14",
 "FileMaxSize","definition","TRUE","Information","Setting 'Autogrow' for data files","Check 'autogrow' setting. Currently maximum size of @{maxsize_in_mb} MBs is set for @{type_desc} file @{fileName} in database @{databaseName}","DefaultRuleset, Performance, DBFileConfiguration","This check verifies the 'autogrow' settings of data files for all system and user databases. In SQL Server, a log file specified with unlimited growth has a maximum size of 2 TB, and a data file has a maximum size of 16 TB. There is no maximum size when this option is specified for a FILESTREAM container. It continues to grow until the disk is full. If there is no space available, performance issues may occur and the database may become unavailable.","https://docs.microsoft.com/sql/t-sql/statements/alter-database-transact-sql-file-and-filegroup-options","Server","Windows Linux",,"SqlServer","[11.0,)",,,
 "FilestreamAccessLevel","definition","TRUE","Information","Non-default value for 'filestream access level' option","Review non-default value @{filestream_access_level} for the 'filestream access level' option","DefaultRuleset, Configuration","The 'filestream access level' option controls the FILESTREAM access level for the instance of SQL Server. By default, this option is disabled, but should be enabled to allow FileStream access or to take advantage of the 'FileTable' feature.","https://docs.microsoft.com/sql/database-engine/configure-windows/filestream-access-level-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
-"FillFactor","definition","TRUE","Information","Non-default value for 'fill factor' option","Review non-default value @{fill_factor} for the 'fill factor' option","DefaultRuleset, Performance, Configuration","The 'fill factor' option controls the default fill factor that is used when a new index is created or rebuilt. The default value is 0, which means that the leaf level of the index will be filled with the highest possible number of rows. This option is an advanced option and should be changed only by an experienced database administrator or certified SQL Server professional.","https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/configure-the-fill-factor-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"FillFactor","definition","TRUE","Information","Non-default value for 'fill factor' option","Review non-default value @{fill_factor} for the 'fill factor' option. A low, nonzero 'fill factor' option value can decrease database read performance","DefaultRuleset, Performance, Configuration","The 'fill factor' option controls the default fill factor that is used when a new index is created or rebuilt. The default value is 0, which means that the leaf level of the index will be filled with the highest possible number of rows.","https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/configure-the-fill-factor-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,"80",
+"FreeSpaceScansPerSec","definition","TRUE","Low","High free space scans rate","Add clustered indexes to heaps and reduce FreeSpace Scans/sec (@{freespace_scans_sec:0.##}) per Batch requests/sec (@{batch_request_sec:0.##}), which is greater than @{threshold:P0}","DefaultRuleset, Performance","Inserts into heaps require SQL Server to perform free space scans to identify pages with free space to insert rows. An insert into a heap often spends time searching for a location to insert the new row. On the other hand the insert into a clustered table does not have to spend any time searching for space. In most cases it is best to start with a clustered index on every table. There are occasional instances where this is not optimal, but it is extremely rare that the existence of a clustered index hurts performance and it usually helps. Test your workload to ensure that adding a clustered index has no detrimental effects.","https://learn.microsoft.com/sql/relational-databases/indexes/heaps-tables-without-clustered-indexes?#when-not-to-use-a-heap","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,"0.1",
 "FtCrawlBandwidthMax","definition","TRUE","Low","Non-default value for 'ft crawl bandwidth (max)' option","Review non-default value @{ft_crawl_bandwidth_max} for the 'ft crawl bandwidth (max)' option as it will be removed in a future version","DefaultRuleset, Configuration","The 'ft crawl bandwidth (max)' option determines the maximum number of buffers that will be maintained by the full-text memory manager in a small buffer pool. A high value will allocate more memory to the indexing process, therefore reducing the available memory for other SQL Server processes.","https://docs.microsoft.com/sql/database-engine/configure-windows/ft-crawl-bandwidth-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
 "FtCrawlBandwidthMin","definition","TRUE","Low","Non-default value for 'ft crawl bandwidth (min)' option","Review non-default value @{ft_crawl_bandwidth_min} for the 'ft crawl bandwidth (min)' option as it will be removed in a future version","DefaultRuleset, Configuration","The 'ft crawl bandwidth (min)' option determines the minimum number of buffers that must be maintained by the full-text memory manager in a small buffer pool. If the SQL Server memory manager requests memory, this minimum number of buffers will generally be maintained.","https://docs.microsoft.com/sql/database-engine/configure-windows/ft-crawl-bandwidth-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
 "FtNotifyBandwidthMax","definition","TRUE","Low","Non-default value for 'ft notify bandwidth (max)' option","Review non-default value @{ft_notify_bandwidth_max} for the 'ft notify bandwidth (max)' option as it will be removed in a future version","DefaultRuleset, Configuration","The 'ft notify bandwidth (max)' option determines the maximum number of buffers that will be maintained by the full-text memory manager in a large buffer pool. A high value will allocate more memory to the indexing process, therefore reducing the available memory for other SQL Server processes.","https://docs.microsoft.com/sql/database-engine/configure-windows/ft-notify-bandwidth-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
 "FtNotifyBandwidthMin","definition","TRUE","Low","Non-default value for 'ft notify bandwidth (min)' option","Review non-default value @{ft_notify_bandwidth_min} for the 'ft notify bandwidth (min)' option as it will be removed in a future version","DefaultRuleset, Configuration","The 'ft notify bandwidth (min)' option determines the minimum number of buffers that must be maintained by the full-text memory manager in a large buffer pool. If the SQL Server memory manager requests memory, this minimum number of buffers will generally be maintained.","https://docs.microsoft.com/sql/database-engine/configure-windows/ft-notify-bandwidth-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"FullScansVsIndexSearches","definition","TRUE","Low","Full scans vs index searches","Reduce the number of Full Scans (@{full_scans_sec:0.##}) versus Index Searches (@{index_searches_sec:0.##})","DefaultRuleset, Performance","Index searches are preferable to index and table scans. For OLTP applications, optimize for more index searches and less scans. An ideal ratio on a typical system would be approximately 1 full scan for every 1000 index searches. Index searches are preferable to full scans because full scans cause excessive disk I/O and consume more CPU resources. Execution plans or extended events can be used to identify which Transact-SQL statements perform scans. Review table and index strategy, and ensure index and statistics maintenance plans are in place.","https://learn.microsoft.com/sql/relational-databases/sql-server-index-design-guide?#General_Design","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,"1000",
 "FullTextDefaultLang","definition","TRUE","Low","Not supported value for 'default full-text language' option","Set 'default full-text language' option to a supported value","DefaultRuleset, Configuration","The value of the 'default full-text language' option is used in a full-text index when no language is specified. If the default full-text language is not supported or the linguistic analysis package is not available, CREATE FULLTEXT INDEX and ALTER FULLTEXT INDEX statements will fail.","https://docs.microsoft.com/sql/database-engine/configure-windows/configure-the-default-full-text-language-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
 "FullTextNoiseWords","definition","TRUE","Information","Non-default value for 'transform noise words' option","Review non-default value @{transform_noise_words} for the 'transform noise words' option","DefaultRuleset, Configuration","If a query using a full-text search predicate contains a noise word (for example, is, the, and) and this configuration setting has been disabled, a warning will be issued and no rows from the query will be returned. The default setting for this option is 0, which indicates that it is off. Enabling this configuration by changing the default to 1 will force noise words to be replaced with an asterisk (*) in the query instead.","https://docs.microsoft.com/sql/database-engine/configure-windows/transform-noise-words-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
 "FullTextPHTimeout","definition","TRUE","Information","Non-default value for 'PH timeout' option","Review non-default value @{PH_timeout} for the 'PH timeout' option","DefaultRuleset, Configuration","The 'PH timeout' option controls the number of seconds that the full-text protocol handler will wait to connect to a database before reaching the timeout threshold. You can increase the 'PH timeout' value when connection attempts are timing out due to temporary network issues.","https://docs.microsoft.com/sql/database-engine/configure-windows/ph-timeout-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
 "InDoubtXactResolution","definition","TRUE","Information","Non-default value for 'in-doubt xact resolution' option","Review non-default value @{in_doubt_xact_resolution} for the 'in-doubt xact resolution' option","DefaultRuleset, Configuration","The 'in-doubt xact resolution' option controls the default outcome of unresolved Microsoft Distributed Transaction Coordinator (MS DTC) transactions. The default value of 0 means that recovery will fail if MS DTC cannot resolve the in-doubt transactions. Before changing this default, you should consider the effect of your application distributed transactions and make sure that no data integrity issues will occur based on partially committed or aborted activity.","https://docs.microsoft.com/sql/database-engine/configure-windows/in-doubt-xact-resolution-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
 "InstantFileInitialization","definition","TRUE","High","Instant file initialization (IFI) is disabled","Enable instant file initialization","DefaultRuleset, DBConfiguration, Performance","Instant file initialization (IFI) allows for faster execution of the previously mentioned file operations, since it reclaims used disk space without filling that space with zeros. Instead, disk content is overwritten as new data is written to the files.","https://docs.microsoft.com/en-us/sql/relational-databases/databases/database-instant-file-initialization","Server","Windows",,"SqlServer","[11.0.7001,12.0) [12.0.6024,13.0) [13.0.4001,)",,,
 "JdbcModuleVersion","definition","TRUE","Medium","JDBC Driver for SQL Server version is not supported","Update JDBC Driver for SQL Server. Current product version @{file_version} of JDBC Driver for SQL Server is out of support","DefaultRuleset, Performance, Security","The JDBC Driver for SQL Server is a Type 4 Java Database Connectivity (JDBC) 4.2 compliant driver that provides robust data access to SQL Server, Azure SQL Database, and Azure SQL Managed Instance. Java connectivity support is continually improving. It is highly recommend to use the latest version of JDBC driver for SQL Server.","https://docs.microsoft.com/sql/connect/jdbc/understanding-xa-transactions","Server","Windows Linux",,"SqlServer","[11.0,)",,,
+"LatchWaitTimePerSec","definition","TRUE","Low","High latch wait time","Investigate and resolve the cause of high average Latch Wait Times (@{total_latch_wait_time_ms:0.##} ms for @{latch_waits_sec:0.##} per second)","DefaultRuleset, Performance","The storage engine must ensure that no other task modifies the contents of a memory structure (like a buffer page) while it is being modified by the current task. It does this by acquiring a latch, updating the row in memory (or any other structure protected by a latch), and then releasing the latch. A latch wait indicates the number of times that a latch could not be granted immediately and the task needed to wait.","https://learn.microsoft.com/sql/relational-databases/diagnose-resolve-latch-contention","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,"10",
+"LazyWritesPerSec","definition","TRUE","Low","Excessive Lazy Writes","Find and troubleshoot the cause of excessive Lazy writes per second (@{lazy_writes:0.##})","DefaultRuleset, Performance","This counter tracks how many times a second that the Lazy Writer process is moving dirty pages from the buffer to disk in order to free up buffer space. Typically, this should not be more than 20 per second. Ideally, it should be close to zero. This issue usually indicates memory pressure. Even if you can add physical memory to the server to mitigate this issue in the short-term, it is better to find the root cause, commonly inefficient queries, and troubleshoot those. Improving the indexing design, reducing cursor usage, and avoiding scans can significantly improve the value for this counter.","https://learn.microsoft.com/sql/relational-databases/writing-pages","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,"20",
 "LockedPagesInMemory","definition","TRUE","High","Lock pages in memory","Enable the 'Lock pages in memory' option","DefaultRuleset, Performance, Memory","This Windows policy determines which accounts can use a process to keep data in physical memory, preventing the system from paging the data to virtual memory on disk.","https://docs.microsoft.com/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-checklist","Server","Windows","AzureVm","SqlServer","[11.0,)",,,
 "LockedPagesInMemory","override","TRUE","Low",,,"",,,,,,,"[11.0.7001, 12.0) [12.0.6024, 13.0) [13.0.4001,)",,,
+"LockRequestsPerSec","definition","TRUE","Low","Lock requests per batch","Review the design of high-read queries and attempt to reduce the number of reads (@{lock_requests_sec:0.##} lock requests for @{batch_request_sec:0.##} batch requests)","DefaultRuleset, Performance","Lock Requests/sec reports the number of requests for a type of lock per second. A Lock Requests/sec greater than 500 when compared to Batch Request/sec indicates that batches are acquiring a large number of locks. This suggests inefficient queries. The risk is that blocking may occur. Review high-read queries. In addition, try to reduce the number of reads by tuning your application, the queries executed by the application and the indexing strategy. You can reduce the locks by changing the transaction isolation level, where appropriate.","https://learn.microsoft.com/sql/relational-databases/sql-server-transaction-locking-and-row-versioning-guide?#Lock_Engine","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,"500",
+"LockWaitTime","definition","TRUE","Low","Excessive Lock Waits","Investigate the cause of excessive Lock Waits (@{lock_wait_time_ms:0.##} ms.) and resolve lock contention","DefaultRuleset, Performance","Excessive locking reduces overall throughput and increases the latency observed by users. Investigate the cause of lock contention and reduce this as much as possible to resolve lock wait issues. The following methods can be used to reduce lock contention and increase overall throughput: review index straegy, leverage Read Committed Snapshot and Snapshot Isolation whenever possible, avoid situations in which many processes are attempting to perform updates or inserts on the same data page, avoid transactions that include user interaction, keep transactions that modify data as short as possible, keep transactions in one batch, avoid pessimistic locking hints such as holdlock whenever possible, and reduce the fill factor when creating an index to help diminish the chance of random updates requiring the same page.","http://support.microsoft.com/kb/75722","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,"500",
 "MaxFTCrawlRange","definition","TRUE","Information","Non-default value for 'max full-text crawl range' option","Review non-default value @{max_full_text_crawl_range} for the 'max full-text crawl range' option","DefaultRuleset, Configuration","The 'max full-text crawl range' option sets the number of partitions that SQL Server will use during a full-text index crawl. The default option is 4. However, you can increase this value if you want to optimize the crawl performance and you have sufficient CPU capacity.","https://docs.microsoft.com/sql/database-engine/configure-windows/max-full-text-crawl-range-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
 "MaxTextReplSize","definition","TRUE","Information","Non-default value for 'max text repl size' option","Review non-default value @{max_text_repl_size} for the 'max text repl size' option","DefaultRuleset, Configuration","The 'max text repl size' option sets the maximum bytes of varchar(max), nvarchar(max), varbinary(max), xml, image, text, and ntext data that can be replicated in a single INSERT, UPDATE, WRITETEXT, or UPDATETEXT operation. If your data modifications exceed this value on replicated columns, you must increase it.","https://docs.microsoft.com/sql/database-engine/configure-windows/configure-the-max-text-repl-size-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
 "MediaRetention","definition","TRUE","Information","Non-default value for 'media retention' option","Review non-default value @{media_retention} for the 'media retention' option","DefaultRuleset, Configuration, Backup","The 'media retention' option sets the default length of time to retain a backup set for the Microsoft SQL Server instance. This default length of time protects the set from being overwritten until the specified number of days has elapsed. The default for this configuration is 0 days. However, you can modify it, based on your own corporate policies.","https://docs.microsoft.com/sql/database-engine/configure-windows/configure-the-media-retention-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
 "MemOptDBResPool","definition","TRUE","Low","In-Memory OLTP database without separate resource pool","Bind In-Memory OLTP database to separate resource pool","Memory, Performance, DefaultRuleset","A databases with memory-optimized tables should be bound to a separate resource pool.","https://docs.microsoft.com/sql/relational-databases/in-memory-oltp/bind-a-database-with-memory-optimized-tables-to-a-resource-pool#bkmk_DefineBinding","Database",,,"SqlServer","[12.0,)",,,
+"MemoryGrantsPending","definition","TRUE","Low","Memory grants pending","Tune queries to reduce Memory Grants Pending (@{memory_grants_pending})","DefaultRuleset, Performance","Memory Grants Pending records the number of connections that are waiting for memory before they can begin processing a memory intensive query such as a sort or hash operation. Connections that wait in this state for a long enough time will eventually get an 8645 error (A time out occurred while waiting for memory resources to execute the query. Rerun the query). If this counter remains above zero for a significant period of time, you will need to determine which queries are doing sorts or hashes and will then need to tune them to see if they can utilize a more efficient plan.","https://techcommunity.microsoft.com/t5/sql-server-blog/understanding-sql-server-memory-grant/ba-p/383595","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"MinServerMemory","definition","TRUE","Information","Non-default value for 'min server memory (MB)' option","Review non-default value @{min_server_memory} for the 'min server memory (MB)' option","DefaultRuleset, Configuration","Use the 'min server memory (MB)' option to guarantee a minimum amount of memory available to the SQL Server Memory Manager. The default value for this option is 0. Leave this option at the default value if the SQL Server instance is on a dedicated computer or node that has no other applications or SQL Server instances running concurrently with it.","https://docs.microsoft.com/sql/database-engine/configure-windows/server-memory-server-configuration-options","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
 "MoreIndexesThanCols","definition","TRUE","Information","Tables with more indexes than columns","Consider removing potentially unnecessary indexes on table @{SchemaName}.@{TableName} that has more indexes than columns","DefaultRuleset, Performance, Indexes","One or more database tables have been identified as having more indexes than columns. During inserts, updates and deletes, every index on a table has to be evaluated and, potentially, updated. If too many indexes exist, SQL Server will spend unnecessary resources maintaining indexes that may not be used. This can significantly affect the amount of disk I/O generated and, subsequently, performance.","https://docs.microsoft.com/sql/relational-databases/sql-server-index-design-guide","Database","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)","NOT: master model msdb tempdb",,
-"OneDbPerPool","definition","TRUE","Low","One database per resource pool","Check whether only one database is bound to resource pool @{pool_name}","Memory, Performance, DefaultRuleset","Only one database should be bound to a resource pool.","https://docs.microsoft.com/sql/relational-databases/resource-governor/resource-governor-resource-pool","Database",,,"SqlServer","[12.0,)",,,
+"NestedTriggers","definition","TRUE","Information","Non-default value for 'nested triggers' option","Review non-default value @{nested_triggers} for the 'nested triggers' option","DefaultRuleset, Configuration","The 'nested triggers' option controls whether an AFTER trigger can cascade. When set to 0, AFTER triggers cannot cascade. The default value for this option is 1.","https://docs.microsoft.com/sql/database-engine/configure-windows/configure-the-nested-triggers-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"OForwardedRecordsPerSec","definition","TRUE","Low","High forwarded records rate","Evaluate index design to reduce Forwarded Records/sec (@{forwarded_records_sec:0.##}) per Batch requests/sec (@{batch_request_sec:0.##}), which is greater than @{threshold:P0}","DefaultRuleset, Performance","Forwarded records occur when a data record in a heap increases in size and the record's current page does not have the space to store the size increase. The record is moved to a new location, becoming a forwarded record, and the forwarding record is left in the original location to point to the real location of the record. The forwarded record points back to the forwarding record in case its location ever needs to change again. If the table experiences several forward records may indicate the table is fragmented and scanning through the table is very inefficient. Review the table index strategy. Forwarded records can be avoided by:Evaluating creating clustered indexes on heaps. Using default values so that an update does not result in a longer row that is the root cause of the forwarded records. Using a fixed size data type such as CHAR instead of VARCHAR. ALTER TABLE … REBUILD to remove heap fragmentation.","https://techcommunity.microsoft.com/t5/sql-server-blog/knowing-about-forwarded-records-can-help-diagnose-hard-to-find/ba-p/383189","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,"0.1",
+"OneDbPerPool","definition","TRUE","Low","One database per resource pool","Check whether only one database is bound to resource pool '@{pool_name}'","Memory, Performance, DefaultRuleset","Only one database should be bound to a resource pool.","https://docs.microsoft.com/sql/relational-databases/resource-governor/resource-governor-resource-pool","Database",,,"SqlServer","[12.0,)",,,
 "OpenObjects","definition","TRUE","Low","Non-default value for 'open objects' option","Review non-default value @{open_objects} for the 'open objects' option as it has no effect and will be removed in a future version","DefaultRuleset, Performance, Configuration","The 'open objects' option has no effect and will be removed in a future version of Microsoft SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use this feature.","https://docs.microsoft.com/sql/database-engine/configure-windows/open-objects-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"OpenTranSleepingSessions","definition","TRUE","Medium","Sleeping sessions with open transactions","Ensure that client applications use transactions efficiently","DefaultRuleset, Performance","In any database, mismanagement of transactions often leads to contention and performance problems in systems that have many users. As the number of users that access the data increases, it becomes important to have applications that use transactions efficiently.","https://docs.microsoft.com/sql/relational-databases/sql-server-transaction-locking-and-row-versioning-guide#controlling-transactions","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"OrphanedAuditSpec","definition","TRUE","Low","Orphaned server audit specification","Connect orphaned audit specification @{spec_name} to a server audit","DefaultRuleset, Configuration, Audit","The server audit specification collects server-level action groups raised by the Extended Events feature. These actions are sent to the audit, which records them in the target. Deliting server audit may cause an orphaned audit specification. Because an audit with a matching GUID does not exist on the server instance, no audit events will be recorded.","https://learn.microsoft.com/sql/relational-databases/security/auditing/sql-server-audit-database-engine","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"OrphanedDbAuditSpec","definition","TRUE","Low","Orphaned database audit specification","Connect orphaned audit specification @{spec_name} to a server audit","DefaultRuleset, Configuration, Audit","The database audit specification collects database-level audit actions raised by the Extended Events feature. These actions are sent to the audit, which records them in the target. Deliting server audit or attaching a database that has an audit specification may cause an orphaned audit specification. Because an audit with a matching GUID does not exist on the server instance, no audit events will be recorded.","https://learn.microsoft.com/sql/relational-databases/security/auditing/sql-server-audit-database-engine","Database","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"OrphanedDbAuditSpec","override","False","Low",,,"",,,,,,"Standard, Express","[11.0, 13.0.4001)",,,
 "OsLoadedModules","definition","TRUE","Low","Third-party modules are loaded into SQL Server process address space","Evaluate impact of loading '@{module}' module into SQL Server process address space","DefaultRuleset, Performance, Security","Certain modules and filter drivers can be loaded into a system that is running SQL Server. In this case, you may experience performance degradation and consistency issues of SQL Server Database Engine.","https://docs.microsoft.com/troubleshoot/sql/performance/performance-consistency-issues-filter-drivers-modules","Server","Windows",,"SqlServer","[11.0,)",,,
+"PageLifeExpectancy","definition","TRUE","Low","Low page life expectancy","Investigate the reason for low page life expectancy (@{page_life_expectancy})","DefaultRuleset, Performance, Memory","The low page life expectancy counter is too low. This may indicate high turnover of data in the buffer pool, which may lead to reduced performance because of high physical memory I/O.","https://learn.microsoft.com/sql/relational-databases/performance-monitor/monitor-memory-usage","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,"700",
+"PageLookupsPerSec","definition","TRUE","Low","High page lookups frequency","Tune queries with high logical disk I/O to lower the page lookups per second (@{page_lookups_sec:0.##}) compared to batch requests (@{batch_request_sec:0.##})","DefaultRuleset, Performance","Page Lookups/sec indicates the number of requests per second to find a page in the buffer pool. While this identifies queries that are accessing data in memory, which is good, when divided by batch requests, a high value indicates that each batch request has many page lookups which signifies inefficeiency. Use database management objects (DMOs) to identify queries with high logical disk I/O. Tune these queries to lower disk IO, which will, in turn, lower the page lookups per second compared to batch requests. A high number of Page Lookups/sec indicates that there have been inefficient plans being generated and too many pages are getting looked up. Review table and index strategy, and ensure index and statistics maintenance plans are in place. A high number of Page Lookups/sec indicates that there have been inefficient plans being generated and too many pages are getting looked up. Review table and index strategy, and ensure index and statistics maintenance plans are in place.","https://learn.microsoft.com/sql/relational-databases/performance-monitor/sql-server-buffer-manager-object","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,"100",
+"PageSplitsPerSec","definition","TRUE","Low","High page split rate","Evaluate why the Page Splits/sec is high and investigate the use of index padding to reduce Page Splits/sec (@{page_splits_sec:0.##}) per Batch requests/sec (@{batch_request_sec:0.##})","DefaultRuleset, Performance","Splitting a page is a complicated operation and the DML statement that initiated the page split generates excessive I/O, and must wait until the split operation completes. Heavily fragmented indexes may be the result of high Page Splits/sec. You can add a fill factor to your index to leave space for new records. You should consider that this will have no effect if records are added sequentially for this index, because all records will be added to the last page.","https://learn.microsoft.com/sql/relational-databases/performance-monitor/sql-server-access-methods-object","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,"0.2",
 "PlansUseRatioNotOptimal","definition","TRUE","Information","Cache needs to be cleared of single-use plans","Check if the plan cache needs to be cleared. Current amount of single-use plans in cache is high (@{SingleUsePlansUseRatio:P0})","DefaultRuleset, Performance, QueryOptimizer","Setting the 'Optimize for ad hoc workloads' option to 1 affects only new plans; plans that are already in the plan cache are unaffected. Make sure to check whether you need to clear the cache from the old single-use plans that may continue to remain.","https://docs.microsoft.com/sql/database-engine/configure-windows/optimize-for-ad-hoc-workloads-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,"0.5",
-"PoolMemParamSet","definition","TRUE","Low","Set 'min_memory_percent' or 'max_memory_percent' parameters","Set 'min_memory_percent' or 'max_memory_percent' for resource pool @{pool_name}","Memory, Performance, DefaultRuleset","A dedicated resource pool should have either 'min_memory_percent' parameter or 'max_memory_percent' parameter set explicitly. You should not let both parameters have default values at the same time.","https://docs.microsoft.com/sql/relational-databases/in-memory-oltp/bind-a-database-with-memory-optimized-tables-to-a-resource-pool","Database",,,"SqlServer","[12.0,)",,,
+"PoolMemParamSet","definition","TRUE","Low","Set 'min_memory_percent' or 'max_memory_percent' parameters","Set 'min_memory_percent' or 'max_memory_percent' for resource pool '@{pool_name}'","Memory, Performance, DefaultRuleset","A dedicated resource pool should have either 'min_memory_percent' parameter or 'max_memory_percent' parameter set explicitly. You should not let both parameters have default values at the same time.","https://docs.microsoft.com/sql/relational-databases/in-memory-oltp/bind-a-database-with-memory-optimized-tables-to-a-resource-pool","Database",,,"SqlServer","[12.0,)",,,
 "PrecomputeRank","definition","TRUE","Low","Non-default value for 'precompute rank' option","Review non-default value @{precompute_rank} for the 'precompute rank' option as it has no effect and will be removed in a future version","DefaultRuleset, Configuration","The 'precompute rank' option has no effect and will be removed in a future version of Microsoft SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use this feature.","https://docs.microsoft.com/sql/database-engine/discontinued-database-engine-functionality-in-sql-server","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
 "QueryGovernorCostLimit","definition","TRUE","Information","Non-default value for 'query governor cost limit' option","Review non-default value @{query_governor_cost_limit} for the 'query governor cost limit' option","DefaultRuleset, Performance, Configuration","The 'query governor cost limit' option indicates the longest time period in seconds that a query can run. Queries with estimated run times longer than this will not run and will return an error. This can result in critical queries not running on your server.","https://docs.microsoft.com/sql/database-engine/configure-windows/configure-the-query-governor-cost-limit-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"RecompilationsPerSec","definition","TRUE","Low","High SQL recompilation rate","Investigate and resolve the cause of high SQL Re-Compilations/sec (@{sql_recompilations_sec:0.##}) per SQL Compilations/sec (@{sql_compilations_sec:0.##}) ","DefaultRuleset, Performance","SQL Server Recompilations/sec is the number of statement recompiles per second. This counts the number of times statement recompiles are triggered. Generally, you want the recompiles to be low. Use dynamic management views and functions to detect queries with the most recompilations. If recompilations are caused by changes in the data then they are necessary, but you should modify statements that cause unnecessary recompilations.","https://learn.microsoft.com/sql/relational-databases/performance-monitor/sql-server-sql-statistics-object","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,"0.1",
+"RemoteAccess","definition","TRUE","Low","Non-default value for 'remote access' option","Review non-default value @{remote_access} for the 'remote access' option as it will be removed in a future version","DefaultRuleset, Configuration","The 'remote access' option controls the execution of stored procedures from local or remote servers. The default value for this option is 1. This grants permission to run local stored procedures from remote servers or remote stored procedures from the local server.","https://docs.microsoft.com/sql/database-engine/configure-windows/configure-the-remote-access-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
 "RemoteDAC","definition","TRUE","Low","Non-default value for 'remote admin connections' option","Review non-default value @{remote_admin_connections} for the 'remote admin connections' option","DefaultRuleset, Security, Configuration","The 'remote admin connections' option enables remote connections to the dedicated administrator connection (DAC) on a Microsoft SQL Server instance. By default, this option is disabled and allows only a local client connection to the DAC. Leave this option disabled if you want to restrict DAC access to only the local client on the stand-alone server. If your SQL Server instance is on a cluster or if you want to use the DAC connection remotely and for some troubleshooting scenarios, you should enable this option.","https://docs.microsoft.com/sql/database-engine/configure-windows/remote-admin-connections-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"RemoteLoginTimeout","definition","TRUE","Information","Non-default value for 'remote login timeout (s)' option","Review non-default value @{remote_login_timeout} for the 'remote login timeout (s)' option","DefaultRuleset, Configuration","The 'remote login timeout (s)' option specifies the number of seconds to wait before returning from a failed attempt to log in to a remote server. The default value for this option is 10.","https://docs.microsoft.com/sql/database-engine/configure-windows/configure-the-remote-login-timeout-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
 "RemoteProcTrans","definition","TRUE","Low","Non-default value for 'remote proc trans' option","Review non-default value @{remote_proc_trans} for the 'remote proc trans' option as it will be removed in a future version","DefaultRuleset, Configuration","The 'remote proc trans' option is used to protect the actions of a server-to-server procedure through a Microsoft Distributed Transaction Coordinator (MS DTC) transaction.","https://docs.microsoft.com/sql/database-engine/configure-windows/configure-the-remote-proc-trans-server-configuration-option","Server","Windows",,"SqlServer, ManagedInstance","[11.0,)",,,
 "ReplicationXPs","definition","TRUE","Low","Non-default value for 'Replication XPs' option","Set 'Replication XPs' option to default. This option is for internal use only.","DefaultRuleset, Configuration, Security","The 'Replication XPs' option opens a significant attack surface area that can be used by an attacker to gather information about the system and potentially abuse the privileges of SQL Server.","https://docs.microsoft.com/sql/database-engine/configure-windows/replication-xps-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ScanPointRevalidation","definition","TRUE","Low","Frequent scan point revalidations","Review clustered index placement to reduce Scan Point Revalidations/sec (@{scan_point_revalidations_sec:0.##})","DefaultRuleset, Performance","During a range scan on an index, there is an optimization that allows skipping the check of individual rows against a range if it is known that all rows on a page satisfy the range. Whenever a scan places a latch on a page, it tries to qualify the entire page for the range. If the check succeeds, a latch is maintained on the page for the duration of the scan (rather than on the individual rows). Another process can cause the latch to be released, however, by modifying the page. If a page latch has to be released, the scan point must be revalidated when the scan resumes. This is because all rows may no longer meet the scan criteria.","https://learn.microsoft.com/sql/relational-databases/performance-monitor/sql-server-access-methods-object","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,"10",
+"ServerTriggerRecursion","definition","TRUE","Information","Non-default value for 'server trigger recursion' option","Review non-default value @{server_trigger_recursion} for the 'server trigger recursion' option","DefaultRuleset, Configuration","The 'server trigger recursion' option controls whether to allow server-level triggers to fire recursively. When set to 0, server-level triggers cannot be fired recursively. The default value for this option is 1.","https://docs.microsoft.com/sql/database-engine/configure-windows/server-trigger-recursion-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"ShowAdvancedOptions","definition","TRUE","Information","Option 'show advanced options' is enabled","Disable 'show advanced options' option","DefaultRuleset, Configuration","Some configuration options are designated as advanced options. By default, these options are not available for viewing and changing. When you set 'show advanced options' option to 1, you can list the advanced options by using 'sp_configure' system stored procedure. It is recommended to only use this state temporarily and switch back to 0 when done with the task that required viewing the advanced options.","https://docs.microsoft.com/sql/database-engine/configure-windows/show-advanced-options-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
 "SMOAndDMOXPs","definition","TRUE","Information","Option 'SMO and DMO XPs' is disabled","Enable 'SMO and DMO XPs' option","DefaultRuleset, Configuration","The 'SMO and DMO XPs' option determines whether SQL Server Management Objects (SMO) and SQL Server Distributed Management Objects (SQL-DMO) XPs are available. The default for this option is enabled to allow various tools and install packages, including SQL Server hotfixes, to work correctly.","https://docs.microsoft.com/sql/database-engine/configure-windows/smo-and-dmo-xps-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
 "SysAdminDefaultDatabase","definition","TRUE","Low","Sysadmin logins use non-master default database","Set sysadmin logins to use 'master' as default database","DefaultRuleset, Configuration","This check verifies whether your SQL Sever logins are members of the 'System Administrators' role that use a non-master default database. Sysadmin logins that use a non-master default database impose administrative risks in cases when user databases are dropped.",,"Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"TempDBFilesInitialSize","definition","TRUE","Medium","Tempdb data files initial size","Preallocate space for all tempdb files by setting the file size to a value large enough to accommodate the typical workload in the environment","DefaultRuleset, TempDB, Performance, DBFileConfiguration","The size and physical placement of the tempdb database can affect the performance of a system. If the size that's defined for tempdb is too small, part of the system-processing load might be taken up with autogrowing tempdb. Space preallocation prevents tempdb from expanding too often, which affects performance.","https://learn.microsoft.com/sql/relational-databases/databases/tempdb-database#optimizing-tempdb-performance-in-sql-server","Server","Windows Linux",,"SqlServer","[11.0,)",,"8",
 "TempDbSameVolume","definition","TRUE","Medium","Tempdb and user databases should not share volumes","Place tempdb on a separate volume. Tempdb and user databases share volume @{volume_mount_point}","DefaultRuleset, Performance, DBFileConfiguration","The tempdb system database is used for temporary objects, internal objects and row versions. Tempdb is often heavily used when queries are executed and, if it has files placed on the same volume as user database files, there can be contention for the IO resources.","https://docs.microsoft.com/sql/relational-databases/databases/tempdb-database","Database","Windows","@{not=AzureVm}","SqlServer","[11.0,)","tempdb",,
 "TwoDigitYearCutoff","definition","TRUE","Information","Non-default value for 'two digit year cutoff' option","Set 'two digit year cutoff' option to default","DefaultRuleset, Configuration","The 'two digit year cutoff' option is used to define the two digit year cutoff value when specifying two-digit years in place of four-digit years. Changing this to a non-default value could have unexpected results if the non-default value is inconsistent with other Microsoft SQL Server instances in your environment. This option is an advanced option and should be changed only by an experienced database administrator or certified SQL Server professional.","https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/configure-the-two-digit-year-cutoff-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
 "UserConnections","definition","TRUE","Information","Non-default value for 'user connections' option","Review non-default value @{user_connections} for the 'user connections' option","DefaultRuleset, Performance, Configuration","The 'user connections' option is an advanced option and should be changed only by an experienced database administrator or certified SQL Server professional. Using the 'user connections' option helps avoid overloading the server with too many concurrent connections. You can estimate the number of connections based on system and user requirements.","https://docs.microsoft.com/sql/database-engine/configure-windows/configure-the-user-connections-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
 "UserOptions","definition","TRUE","Information","Non-default value for 'user options' option","Review non-default value @{user_options} for the 'user options' option","DefaultRuleset, Configuration","The 'user options' option defines the user option defaults, such as ARITHABORT, ANSI_WARNINGS, CONCAT_NULL_YIELDS_NULL. The bit positions in user options are identical to those in @@OPTIONS. Each connection has its own @@OPTIONS function, which represents the configuration environment. When logging in to Microsoft SQL Server, a user receives a default environment that assigns the current user options value to @@OPTIONS. Executing SET statements for user options affects the corresponding value in the session's @@OPTIONS function. All connections created after this setting is changed, receive the new value.","https://docs.microsoft.com/sql/database-engine/configure-windows/configure-the-user-options-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"WaitsForWorker","definition","TRUE","Low","High Wait for the worker","Investigate the queries and batches that are holding the threads for the longest duration and engage in fine tuning those queries/batches.Wait for the worker\Average wait time (ms) (@{wait_for_the_worker}) is greater than @{threshold}","DefaultRuleset, Performance, CPU","SQL Server Wait Statistics\Wait for Worker counter indicates average time that each SQL Server session is waiting for a worker thread to become available. If the max worker thread setting is set to default, do not increase it. If you configure a number of worker threads to a value that is greater than the default, it is almost always counterproductive and slows performance because of scheduling and resource overhead. Instead, investigate the queries and batches that are holding the threads for the longest duration and engage in fine tuning those queries/batches. Only increase this setting under very unusual circumstances and when rigorous methodical testing demonstrates that it is useful to do so.","https://learn.microsoft.com/sql/database-engine/configure-windows/configure-the-max-worker-threads-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,"500",
+"WaitsLogWrite","definition","TRUE","Low","High transaction log disk response time","Improve the disk response time for the drives where the Transaction log resides, especially for write operations, log write waits\Average wait time (ms) (@{log_write_waits}) is greater than @{threshold}","DefaultRuleset, Performance","A high number of waits on Log Writes has been detected. Before any modification to a table can take place, SQL Server must write a record to the Transaction log. Any waits that occur during writes to the Transaction log will result in performance degradation. Evaluate disk performance to identify disk bottlenecks then correlate with SQL Server transactions and tune them.","https://learn.microsoft.com/troubleshoot/sql/performance/troubleshoot-sql-io-performance#writelog","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,"500",
+"WaitsNetworkIO","definition","TRUE","Low","High Network IO","Investigate the cause of high Network I/O Waits and resolve the issues that you find, network IO waits\Average wait time (ms) (@{network_io_waits}) is greater than @{threshold}","DefaultRuleset, Performance","Waits on the network I/O are frequently caused by clients not completely processing all data returned by a query or network saturation. Unprocessed results will sit in the output buffer and the SPID will show a wait type for the network I/O until all the results have been received by the client. This introduces the risk of performance degradation. Identify the queries that are waiting on the network I/O and ensure that clients are processing all the results of the query. If you have any network saturation between the server and the application, work to reduce that saturation increasing the number or speed of switches and network cards that are saturated","https://learn.microsoft.com/troubleshoot/sql/performance/troubleshoot-query-async-network-io","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,"500",
+"WaitsNonPageLatch","definition","TRUE","Low","High non-Page latch waits","Non-Page latch waits (@{non_page_latch_waits}) is greater than @{threshold}, take snapshots from sys.dm_os_latch_stats to identify the specific latch class, the identify the queries that are waiting on Non-Page latch and tune them","DefaultRuleset, Performance","The SQL Server Wait Statistics\Non-Page Latch Waits counter indicates the average time that each SQL Server session is waiting on non-page latches. Latches are used to synchronize access to cached data pages and other in-memory objects. Typically, latches are only held briefly, and latch wait times should be correspondingly small. A high number for this counter means that many processes are waiting for latch classes that are not related to buffers which, depending on the latch class, could affect your workload.","https://learn.microsoft.com/sql/relational-databases/diagnose-resolve-latch-contention","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,"500",
+"WaitsPageIOLatch","definition","TRUE","Low","High Page IO latch waits","Review the disk performance counters including Physical Disk: Disk Sec/Read and Disk Sec/Write and resolve the cause of the high SQL Server Page IO latch wait times (@{page_io_latch_waits} ms), and SQL Server Buffer Manager: Page Life Expectancy to investigate whether there are any disk subsystem issues, review index straegy and query plan for TOP queries with high number of logical reads","DefaultRuleset, Performance","The IO latches are a subset of BUF buffer latches that are used when the buffer and associated data page or the index page is in the middle of an I/O operation. PAGEIOLATCH wait types are used for disk-to-memory transfers and a significant wait time for these wait types suggests disk I/O subsystem issues.","https://learn.microsoft.com/troubleshoot/sql/performance/troubleshoot-sql-io-performance","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,"500",
+"WaitsPageLatch","definition","TRUE","Low","High Page Latch waits","Review latch contention, average page latch wait time is @{page_latch_waits} ms","DefaultRuleset, Performance","The SQL Server Wait Statistics\Page Latch Waits counter indicates the average time that each SQL Server session is waiting for page latches, not including IO latches. Page Latch Waits can cause a bottleneck in your system and a corresponding adverse effect on performance.","https://learn.microsoft.com/sql/relational-databases/diagnose-resolve-latch-contention","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,"500",
+"WorkfilesPerSec","definition","TRUE","Low","High Workfiles Created per second","Review query performance to reduce Workfiles Created per sec (@{workfiles_created_sec:0.##})","DefaultRuleset, Performance, Memory","Workfiles are created by hash operations, and used to store temporary results for hash joins and hash aggregations. SQL Server creates a work file in tempdb when the amount of data being processed is too big to fit into the available memory used for hash operations, and generates a hash warning as a result. Determine the queries that are generating hash warnings using Extended Events.To eliminate or reduce the frequency of hash recursion and bailouts, do one of the following: Make sure that statistics exist on the columns that are being joined or grouped. If statistics exist on the columns, make sure that these are updated. Tune the query to use a different type of join, namely by adding appropriate indexes. Increase available memory on the computer. Hash recursion or bailout occurs when there is not enough memory to process queries in place and they need to spill to disk. Creating or updating the statistics on the column involved in the join is the most effective way to reduce the number of hash recursion or bailouts that occur, namely when appropriate indexes are already in place.","https://learn.microsoft.com/sql/relational-databases/event-classes/hash-warning-event-class","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,"0.2",
 "WorkingSetSize","definition","TRUE","Low","Non-default value for 'set working set size' option","Review non-default value @{set_working_set_size} for the 'set working set size' option as it has no effect and will be removed in a future version","DefaultRuleset, Configuration","The 'set working set size' option has no effect and will be removed in a future version of Microsoft SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use this feature.","https://docs.microsoft.com/sql/database-engine/configure-windows/set-working-set-size-server-configuration-option","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,,
+"WorktablesFromCache","definition","TRUE","Low","Low Worktables from Cache Ratio","Review application memory requirements, Worktables from Cache Ratio is (@{worktables_from_cache_ratio:P0})","DefaultRuleset, Performance, Memory","The Worktables From Cache Ratio counter records the percentage of worktables that were immediately available from the worktable cache. When a query execution plan is cached, the worktables needed by the plan are not dropped across multiple executions of the plan but only truncated. Because the worktable is cached, the next execution of the query is faster. When the system is low on memory, the execution plan may be removed from the cache and the associated worktables dropped as well.","https://learn.microsoft.com/troubleshoot/sql/performance/troubleshoot-memory-issues","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,"0.9",
+"WorktablesPerSec","definition","TRUE","Low","High Worktables Created per second","Review table and index strategy, and ensure index and statistics maintenance plans are in place, Worktables Created/sec (@{worktables_created_sec:0.##}) per Batch requests/sec (@{batch_request_sec:0.##}) is greater than @{threshold:P0}","DefaultRuleset, Performance, Memory","Worktables are internal tables that are used to hold intermediate results. Worktables are generated for certain GROUP BY, ORDER BY, or UNION queries. For example, if an ORDER BY clause references columns that are not covered by any indexes, the relational engine may need to generate a worktable to sort the result set into the order requested. Worktables are also sometimes used as spools that temporarily hold the result of executing a part of a query plan. Worktables are built in tempdb and are dropped automatically when they are no longer needed.","https://learn.microsoft.com/sql/relational-databases/performance-monitor/sql-server-access-methods-object","Server","Windows Linux",,"SqlServer, ManagedInstance","[11.0,)",,"0.2",

samples/manage/sql-assessment-api/docs/Reference/DataTransformation/README.md

@@ -8,5 +8,6 @@
 - [nameValuePairs](nameValuePairs.md)
 - [noData](noData.md)
 - [parse](parse.md)
+- [performance](performance.md)
 - [rename](rename.md)
-- [toString](toString.md)
+- [toString](toString.md)

samples/manage/sql-assessment-api/docs/Reference/DataTransformation/parse.md

@@ -1,4 +1,4 @@
-# Parse <!-- omit in toc -->
+# Data transformation: **parse** <!-- omit in toc -->
 
 The regular expression parser extracts data from substrings of variable values that correspond to the named groups specified in regular expressions.
 

samples/manage/sql-assessment-api/docs/Reference/DataTransformation/performance.md

@@ -0,0 +1,255 @@
+# Data transformation: **performance**
+
+Performance probe returns a table containing multiple samples for all requested counters. A check needs some derived value. E.g. average, maximum, more complex functions.
+
+Use the *Performance* transform in [probe references](../../Customization/ProbeReference.md) to get derived values. Performance transform calculates specified derived value for each counter used by the check.
+
+![Performance transform structure diagram](../../Customization/img/BasicPerformanceTransformStructure.svg)
+
+## Derived value functions
+
+The following table lists available performance value functions.
+
+- **n** – number of samples for this counter
+- **c₁**, **c₂** – sample values for this counter
+- **t₁**, **t₂** – time stamps for samples
+- **b₁**, **b₂** – sample values for *base_counter*
+
+| Type        | Parameter      | Formula                                            |
+|-------------|:--------------:|:--------------------------------------------------:|
+| average     |       –        | $\frac{1}{n}\sum_{i=1}^n c_i$                              |
+| delta_ratio | *base_counter* | $\frac{c_2 - c_1}{b_2 - b_1}$                      |
+| min/max     |       –        | Minimum/maximum of all samples                     |
+| rate        |       –        | $\frac{c_2 - c_1}{t_2 - t_1}$                      |
+| ratio       | *base_counter* | $\left(\frac{c_2}{b_2} + \frac{c_1}{b_1}\right)/2$ |
+
+## Example ruleset
+
+The following JSON object represents a complete rule set using performance counters.
+
+```json
+{
+    "schemaVersion": "1.0",
+    "name": "Performance Checks Example",
+    "version": "1.0",
+    "rules":[
+        {
+            "target": { "type": "Server" },
+            "id": "TotalPages",
+            "itemType": "definition",
+            "displayName": "Buffer Manager Total pages",
+            "description": "Use \"average\", \"min\", or \"max\" for counter type PERF_COUNTER_LARGE_RAWCOUNT(65792).",
+            "message": "Total pages (@{total_pages}) is greater than 0",
+            "condition": {
+                "lt": ["@total_pages", 0]
+            },
+            "probes": [
+                {
+                    "id": "PerformanceProbe",
+                    "transform": {
+                        "type": "performance",
+                        "counters": {
+                            "total_pages": "average"
+                        }
+                    }
+                }
+            ]
+        },
+        {
+            "target": { "type": "Server" },
+            "id": "CacheHitRatio",
+            "itemType": "definition",
+            "displayName": "Buffer Manager cache hit ratio",
+            "description": "Use \"ratio\" for counter type PERF_LARGE_RAW_FRACTION(537003264) and specify base PERF_LARGE_RAW_BASE(1073939712).",
+            "message": "Cache hit ratio (@{cache_hit_ratio:P0}) is greater than 0",
+            "condition": {
+                "lt": ["@cache_hit_ratio", 0]
+            },
+            "probes": [
+                {
+                    "id": "PerformanceProbe",
+                    "transform": {
+                        "type": "performance",
+                        "counters": {
+                            "cache_hit_ratio": {
+                                "type": "ratio",
+                                "base": "cache_hit_ratio_base"
+                            }
+                        }
+                    }
+                }
+            ]
+        },
+        {
+            "target": { "type": "Server" },
+            "id": "LatchWaitTime",
+            "itemType": "definition",
+            "displayName": "Average Latch Wait Time",
+            "description": "Use \"delta_ratio\" for counter type PERF_AVERAGE_BULK(1073874176) and base PERF_LARGE_RAW_BASE(1073939712).",
+            "message": "Average Latch Wait Time (@{latch_wait_time}ms.) is greater than 0",
+            "condition": {
+                "lt": ["@latch_wait_time", 0]
+            },
+            "probes": [
+                {
+                    "id": "PerformanceProbe",
+                    "transform": {
+                        "type": "performance",
+                        "counters": {
+                            "latch_wait_time": {
+                                "type": "delta_ratio",
+                                "base": "latch_wait_time_base"
+                            }
+                        }
+                    }
+                }
+            ]
+        },
+        {
+            "target": { "type": "Server" },
+            "id": "TransactionsPerSec",
+            "itemType": "definition",
+            "displayName": "Database Transactions per sec",
+            "description": "Use \"rate\" for counter type PERF_COUNTER_BULK_COUNT(272696576).",
+            "message": "Transactions per sec (@{transactions_sec:0.##}sec.) for database @{instance_name} is greater than 0",
+            "condition": {
+                "or": [{"eq": ["@instance_name", "_Total"]}, {"le": ["@transactions_sec", 0]}]
+            },
+            "probes": [
+                {
+                    "id": "PerformanceProbe",
+                    "transform": {
+                        "type": "performance",
+                        "counters": {
+                            "transactions_sec": "rate"
+                        }
+                    }
+                }
+            ]
+        },
+        {
+            "target": { "type": "Server" },
+            "id": "TotalTransactionsPerSec",
+            "itemType": "definition",
+            "displayName": "Total Database Transactions per sec",
+            "description": "Use \"rate\" for counter type PERF_COUNTER_BULK_COUNT(272696576).",
+            "message": "Total Transactions per sec (@{transactions_sec:0.##}sec.) is greater than 0",
+            "condition": {
+                "lt": ["@transactions_sec", 0]
+            },
+            "probes": [
+                {
+                    "id": "PerformanceProbe",
+                    "transform": {
+                        "type": "performance",
+                        "counters": {
+                            "transactions_sec": {
+                                "type": "rate", 
+                                "instance": "_Total"
+                            }
+                        }
+                    }
+                }
+            ]
+        }
+    ],
+    "probes":{
+        "PerformanceProbe": [{
+            "type": "Performance",
+            "implementation": {
+                "Counters": {
+                    "Buffer Manager": {
+                        "Buffer cache hit ratio": "cache_hit_ratio",
+                        "Buffer cache hit ratio base": "cache_hit_ratio_base",
+                        "Target pages": "total_pages"
+
+                    },
+                    "Latches": {
+                        "Average Latch Wait Time (ms)": "latch_wait_time",
+                        "Average Latch Wait Time Base": "latch_wait_time_base"
+                    },
+                    "Databases": {
+                        "Transactions/sec": "transactions_sec"
+                    }
+                }
+            }
+        }]
+    }
+}
+```
+
+## How to use multiple performance counters in a single check
+
+While using multiple performance counters for different instances results might not look as expected. Take a look at the following example.
+
+```json
+"probes": [
+    {
+        "id": "PerformanceProbe",
+        "alias": "b",
+        "transform": {
+        "type": "performance",
+            "counters": {
+                "batch_request_sec": "rate",
+                "lock_requests_sec": {
+                    "type": "rate",
+                    "instance": "_Total"
+                }
+            }
+        }
+    }
+]
+```
+
+The code worked as expected. The data transform returned two rows of data from the Performance probe:
+
+| batch_request_sec | lock_requests_sec | instance_name               |
+|:-----------------:|:-----------------:|:---------------------------:|
+|              123s |              null | ‘’ *(no instance selected)* |
+|              Null |              456s |                    ‘_Total’ |
+
+The condition is checked once per row and triggers a message for the first one and an error for another.
+
+The following JSON illustrates a solution. The Performance probe is referenced twice. The first reference gets `batch_request_sec` rate. The second one gets `lock_requests_sec` rate for the `_Total` instance. Note aliases associated with each probe reference.
+
+```json
+"probes": [
+    {
+        "id": "PerformanceProbe",
+        "alias": "b",
+        "transform": {
+        "type": "performance",
+            "counters": {
+                "batch_request_sec": "rate"
+            }
+        }
+    },
+    {
+        "id": "PerformanceProbe",
+        "alias": "l",
+        "transform": {
+        "type": "performance",
+            "counters": {
+                "lock_requests_sec": {
+                    "type": "rate",
+                    "instance": "_Total"
+                }
+            }
+        }
+    }
+]
+```
+
+[Alias](../../Customization/ProbeReference.md#alias) is any alternative name for the probe. Any data variable may be prefixed with an alias or a probe id. E.g. the following names refer to the same value in an unambiguous case:
+
+```plain
+@PerformanceProbe::batch_request_sec
+@b::batch_request_sec
+@batch_request_sec
+```
+
+Those two probe references result in the following data passed to the check:
+
+| b::batch_request_sec | b::instance_name | l::lock_requests_sec| l::instance_name |
+|:--------------------:|:----------------:|:-------------------:|:----------------:|
+|                 123s | ‘’ no instance   |                456s |         ‘_Total’ |

samples/manage/sql-assessment-api/docs/Reference/Probes/Performance.md

@@ -0,0 +1,310 @@
+# Performance probe
+
+**Type code:** *Performance*
+
+Performance probe returns values for performance counters. This probe is meant to be used with [**performance**](../DataTransformation/performance.md) transform.
+
+## Implementation properties
+
+Implementation part of the probe definition contains the following parameters.
+
+| Parameter       | Required | Type   | Default | Description                              |
+|-----------------|:--------:|:------:|:-------:|------------------------------------------|
+| numberOfSamples | Optional | number |    2    | Number of samples taken                     |
+| interval        | Optional | number |    1    | Time interval between samples in seconds |
+| counters        | Required | object |         | The list of performance counters         |
+
+![Performance probe structure diagram](../../Customization/img/BasicPerformanceProbeStructure.svg)
+
+## Performance counters list
+
+The list of performance counters is represented by a JSON object. Each property is for performance objects, e.g. *'Latches'*, *'Databases'*, *'Buffer Manager'*. Each performance object has a JSON object, where each property represents a performance counter.
+
+Counter names often contain spaces and other non-alphanumeric characters. That is why each counter must have an alias. Counter alias is the name which will be used in check conditions and messages.
+
+Optionally, counter may have a list of specific instances of interest.
+
+In the following example the probe retrieves *'Page Allocated/sec'* metric for *'Access Methods'* and returns samples as *page_allocated* values.
+
+```json
+{
+  "type": "Performance",
+  "implementation": {
+    "Counters": {
+      "Access Methods": {
+        "Pages Allocated/sec": "pages_allocated"
+      }
+    }
+  }
+}
+```
+
+In the next example the probe takes only one sample for *'Free Node memory (KB)'*.
+
+```json
+{
+  "type": "Performance",
+  "implementation": {
+    "NumberOfSamples": 1,
+    "Counters": {
+      "Memory Node": {
+        "Free Node Memory (KB)": "free_node_memory"
+      }
+    }
+  }
+}
+```
+
+In the third example the probe returns data for two performance objects *'Memory Node'* and *'Access Methods'*. For the *'Free Node Memory (KB)'* counter it returns data for *'000'* instance only.
+
+```json
+{
+  "type": "Performance",
+  "implementation": {
+    "NumberOfSamples": 1,
+    "Counters": {
+      "Memory Node": {
+        "Free Node Memory (KB)": {
+          "alias": "free_node_memory",
+          "instances": ["000"]
+        },
+        "Target Node Memory (KB)": "target_node_memory"
+      },
+      "Access Methods": {
+        "Pages Allocated/sec": "pages_allocated"
+      }
+    }
+  }
+}
+```
+
+## Example ruleset
+
+The following JSON object represents a complete rule set using performance counters.
+
+```json
+{
+    "schemaVersion": "1.0",
+    "name": "Performance Checks Example",
+    "version": "1.0",
+    "rules":[
+        {
+            "target": { "type": "Server" },
+            "id": "TotalPages",
+            "itemType": "definition",
+            "displayName": "Buffer Manager Total pages",
+            "description": "Use \"average\", \"min\", or \"max\" for counter type PERF_COUNTER_LARGE_RAWCOUNT(65792).",
+            "message": "Total pages (@{total_pages}) is greater than 0",
+            "condition": {
+                "lt": ["@total_pages", 0]
+            },
+            "probes": [
+                {
+                    "id": "PerformanceProbe",
+                    "transform": {
+                        "type": "performance",
+                        "counters": {
+                            "total_pages": "average"
+                        }
+                    }
+                }
+            ]
+        },
+        {
+            "target": { "type": "Server" },
+            "id": "CacheHitRatio",
+            "itemType": "definition",
+            "displayName": "Buffer Manager cache hit ratio",
+            "description": "Use \"ratio\" for counter type PERF_LARGE_RAW_FRACTION(537003264) and specify base PERF_LARGE_RAW_BASE(1073939712).",
+            "message": "Cache hit ratio (@{cache_hit_ratio:P0}) is greater than 0",
+            "condition": {
+                "lt": ["@cache_hit_ratio", 0]
+            },
+            "probes": [
+                {
+                    "id": "PerformanceProbe",
+                    "transform": {
+                        "type": "performance",
+                        "counters": {
+                            "cache_hit_ratio": {
+                                "type": "ratio",
+                                "base": "cache_hit_ratio_base"
+                            }
+                        }
+                    }
+                }
+            ]
+        },
+        {
+            "target": { "type": "Server" },
+            "id": "LatchWaitTime",
+            "itemType": "definition",
+            "displayName": "Average Latch Wait Time",
+            "description": "Use \"delta_ratio\" for counter type PERF_AVERAGE_BULK(1073874176) and base PERF_LARGE_RAW_BASE(1073939712).",
+            "message": "Average Latch Wait Time (@{latch_wait_time}ms.) is greater than 0",
+            "condition": {
+                "lt": ["@latch_wait_time", 0]
+            },
+            "probes": [
+                {
+                    "id": "PerformanceProbe",
+                    "transform": {
+                        "type": "performance",
+                        "counters": {
+                            "latch_wait_time": {
+                                "type": "delta_ratio",
+                                "base": "latch_wait_time_base"
+                            }
+                        }
+                    }
+                }
+            ]
+        },
+        {
+            "target": { "type": "Server" },
+            "id": "TransactionsPerSec",
+            "itemType": "definition",
+            "displayName": "Database Transactions per sec",
+            "description": "Use \"rate\" for counter type PERF_COUNTER_BULK_COUNT(272696576).",
+            "message": "Transactions per sec (@{transactions_sec:0.##}sec.) for database @{instance_name} is greater than 0",
+            "condition": {
+                "or": [{"eq": ["@instance_name", "_Total"]}, {"le": ["@transactions_sec", 0]}]
+            },
+            "probes": [
+                {
+                    "id": "PerformanceProbe",
+                    "transform": {
+                        "type": "performance",
+                        "counters": {
+                            "transactions_sec": "rate"
+                        }
+                    }
+                }
+            ]
+        },
+        {
+            "target": { "type": "Server" },
+            "id": "TotalTransactionsPerSec",
+            "itemType": "definition",
+            "displayName": "Total Database Transactions per sec",
+            "description": "Use \"rate\" for counter type PERF_COUNTER_BULK_COUNT(272696576).",
+            "message": "Total Transactions per sec (@{transactions_sec:0.##}sec.) is greater than 0",
+            "condition": {
+                "lt": ["@transactions_sec", 0]
+            },
+            "probes": [
+                {
+                    "id": "PerformanceProbe",
+                    "transform": {
+                        "type": "performance",
+                        "counters": {
+                            "transactions_sec": {
+                                "type": "rate", 
+                                "instance": "_Total"
+                            }
+                        }
+                    }
+                }
+            ]
+        }
+    ],
+    "probes":{
+        "PerformanceProbe": [{
+            "type": "Performance",
+            "implementation": {
+                "Counters": {
+                    "Buffer Manager": {
+                        "Buffer cache hit ratio": "cache_hit_ratio",
+                        "Buffer cache hit ratio base": "cache_hit_ratio_base",
+                        "Target pages": "total_pages"
+
+                    },
+                    "Latches": {
+                        "Average Latch Wait Time (ms)": "latch_wait_time",
+                        "Average Latch Wait Time Base": "latch_wait_time_base"
+                    },
+                    "Databases": {
+                        "Transactions/sec": "transactions_sec"
+                    }
+                }
+            }
+        }]
+    }
+}
+```
+
+## How to use multiple performance counters in a single check
+
+While using multiple performance counters for different instances an issue the results might not look as expected. Take a look at the following example.
+
+```json
+"probes": [
+    {
+        "id": "PerformanceProbe",
+        "alias": "b",
+        "transform": {
+        "type": "performance",
+            "counters": {
+                "batch_request_sec": "rate",
+                "lock_requests_sec": {
+                    "type": "rate",
+                    "instance": "_Total"
+                }
+            }
+        }
+    }
+]
+```
+
+The code worked as expected. The data transform returned two rows of data from the Performance probe:
+
+| batch_request_sec | lock_requests_sec | instance_name           |
+|:-----------------:|:-----------------:|:-----------------------:|
+|              123s |              null | ‘’ no instance selected |
+|              Null |              456s |                ‘_Total’ |
+
+The condition is checked once per row and triggers a message for the first one and an error for another.
+
+The following JSON illustrates a solution. The Performance probe is referenced twice. The first reference gets `batch_request_sec` rate. The second one gets `lock_requests_sec` rate for the `_Total` instance. Note [aliases](../../Customization/ProbeReference.md#alias) associated with each probe reference.
+
+```json
+"probes": [
+    {
+        "id": "PerformanceProbe",
+        "alias": "b",
+        "transform": {
+        "type": "performance",
+            "counters": {
+                "batch_request_sec": "rate"
+            }
+        }
+    },
+    {
+        "id": "PerformanceProbe",
+        "alias": "l",
+        "transform": {
+        "type": "performance",
+            "counters": {
+                "lock_requests_sec": {
+                    "type": "rate",
+                    "instance": "_Total"
+                }
+            }
+        }
+    }
+]
+```
+
+[Alias](../../Customization/ProbeReference.md#alias) is any alternative name for the probe. Any data variable may be prefixed with an alias or a probe id. E.g. the following names refer to the same value in an unambiguous case:
+
+```plain
+@PerformanceProbe::batch_request_sec
+@b::batch_request_sec
+@batch_request_sec
+```
+
+Those two probe references result in the following data passed to the check:
+
+| b::batch_request_sec | b::instance_name | l::lock_requests_sec| l::instance_name |
+|:--------------------:|:----------------:|:-------------------:|:----------------:|
+|                 123s | ‘’ no instance   |                456s |         ‘_Total’ |

samples/manage/sql-assessment-api/docs/Reference/Probes/README.md

@@ -6,9 +6,10 @@ The SQL Assessment API provides different types of probes to get data for assess
 
 - [AzGraph](./AzGraphProbe.md)
 - [AzMetadata](./AzMetadataProbe.md)
+- [BasicPerformance](./BasicPerformance.md)
 - [CMD](CMDShellProbes.md)
 - [External](CLRProbes.md)
 - [PowerShell](PowerShellProbes.md)
 - [Registry](RegistryProbes.md)
 - [T-SQL](TSQLProbes.md)
-- [WMI](WMIProbes.md)
+- [WMI](WMIProbes.md)

samples/manage/sql-assessment-api/release-notes.md

@@ -14,12 +14,91 @@ Download: [SMO NuGet Package](https://www.nuget.org/packages/Microsoft.SqlServer
 
 You can use GitHub issues to provide feedback to the product team.
 
-## July 2022 - 1.1.9
+## December 2022 - 1.1.17
 
 Version: SqlServer PowerShell module, SqlManagementObjects (SMO) package: not updated
 
 ### What's new
 
+- New rules:
+  - 98 recommendations based on SQL Server error log content
+  - Availability database count
+  - Availability replica recovery health
+  - Columnstore indexes with large page memory model
+  - High SQL compilations frequency
+  - High cursor requests frequency
+  - Backup files on a separate physical location
+  - Database mirroring
+  - High deadlock frequency
+  - SQL Server on a domain controller
+  - Error log retention settings
+  - High free space scans rate
+  - Full scans vs index searches
+  - High latch wait time
+  - Excessive lazy writes
+  - Lock requests per batch
+  - Excessive lock waits
+  - Memory grants pending
+  - Non-default value for 'min server memory (MB)' option
+  - Non-default value for 'nested triggers' option
+  - High forwarded records rate
+  - Sleeping sessions with open transactions
+  - Orphaned server audit specification
+  - Orphaned database audit specification
+  - Low page life expectancy
+  - High page lookups frequency
+  - High page split rate
+  - High SQL recompilation rate
+  - Non-default value for 'remote access' option
+  - Non-default value for 'remote login timeout (s)' option
+  - Frequent scan point revalidations
+  - Non-default value for 'server trigger recursion' option
+  - Option 'show advanced options' is enabled
+  - Tempdb data files initial size
+  - High Wait for the worker
+  - High transaction log disk response time
+  - High Network IO
+  - High non-Page latch waits
+  - High Page IO latch waits
+  - High Page Latch waits
+  - High Workfiles Created per second
+  - Low Worktables from Cache ratio
+  - High Worktables Created per second
+- New probes:
+  - [BasicPerformance](./docs/Reference/Probes/BasicPerformance.md)
+  - AuditSpecs
+  - ComputerSystem
+  - DatabaseBackupsMedia
+  - DatabaseMirroring
+  - ErrorLog
+  - ServerAudits
+  - ServerDatabasesProperties
+  - SysOpenTransactions
+- New transformations:
+  - [Performance](./docs//Reference/Probes/BasicPerformance.md#performance-transform) counter [data transformation](./docs/Customization/DataTransformation.md)
+
+### Bug fixes and improvements
+
+- Add [join](./docs/Reference/DataTransformation/aggregate.md#join) string [aggregate function](./docs/Reference/DataTransformation/aggregate.md#aggregate-functions) new parameters:
+  - **distinct** specifies whether duplicates should be eliminated
+  - **comparison** specifies [StringComparison](https://learn.microsoft.com/dotnet/api/system.stringcomparison) used by the aggregate function
+- Add **ag_replica_recovery_health** variable to the **AGConfiguration** probe
+- Add **age_days** to **ErrorLogInfo** probe
+- Add **remote_access**, **remote_login_timeout**, **server_trigger_recursion**, and **default_language** to **SysConfiguration** probe
+- Fix warning message on missing permissions and other requirements
+- Fix help link for DbSpaceAvailable check ([GitHub #1035](https://github.com/microsoft/sql-server-samples/issues/1035))
+- Fix falsely flagging deprecated features in job steps ([GitHub #1025](https://github.com/microsoft/sql-server-samples/issues/1025))
+- Fix configured to active value comparison for Max and Min server memory
+- Fix duplicate messages for Azure disk checks
+- Fix TF834 check triggered when no columnstore index is in use
+- Remove Server target type filter from probes which work for databases
+
+## July 2022 - 1.1.9
+
+Version: SqlServer PowerShell module: [22.0.30-preview](https://www.powershellgallery.com/packages/SqlServer/22.0.30-preview), SqlManagementObjects (SMO) package: not updated
+
+### What's new
+
 - New rules:
   - Access check cache options ratio
   - Availability group listener network mode