| | DisplayName | Description | ID | Target | Category | Enabled | Instance Name | Counter Name | Frequency | Event_ID | Event Source | Alert Generate | Alert Severity | Alert Priority | Remotable | Event Log |
|---|
 | MSSQL 2016: Alert engine stopped due to unrecoverable local eventlog errors | SQL Server Agent was unable to open the local event log. | Microsoft.SQLServer.2016.Alert_engine_stopped_due_to_unrecoverable_local_eventlog_errors_1_5_Rule | Microsoft.SQLServer.2016.Agent | EventCollection | True | | | 0 | 317 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.Agent"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: An error occurred in a SQL Server Service Broker/Database Mirroring transport connection endpoint | SQL Server uses Service Broker and Database Mirroring endpoints for communication outside of the SQL Server instance. | Microsoft.SQLServer.2016.An_error_occurred_in_a_SQL_Server_Service_Broker_Database_Mirroring_transport_connection_endpoint_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 9642 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: An error occurred in the Service Broker manager | The rule triggers an alert when an error occurred in the SQL Server Service Broker manager. | Microsoft.SQLServer.2016.An_error_occurred_in_the_Service_Broker_manager_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 9645 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: An error occurred in the Service Broker queue rollback handler | SQL Server Service Broker raises MSSQLSERVER event ID 8405 when an error prevents Service Broker from disabling a queue during a rollback. | Microsoft.SQLServer.2016.An_error_occurred_in_the_Service_Broker_queue_rollback_handler_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8405 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: An error occurred in the SQL Server Service Broker message dispatcher | An error occurred in the SQL Server Service Broker message dispatcher. The Windows application log or SQL Server error log may identify the specific error. | Microsoft.SQLServer.2016.An_error_occurred_in_the_SQL_Server_Service_Broker_message_dispatcher_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 9644 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: An error occurred in the SQL Server Service Broker message transmitter | SQL Server Service Broker message transmitter detected an error. | Microsoft.SQLServer.2016.An_error_occurred_in_the_SQL_Server_Service_Broker_message_transmitter_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 28072 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: An error occurred in the SQL Server Service Broker or Database Mirroring transport manager | An error occurred in the SQL Server Service Broker or Database Mirroring transport manager. The Windows application log or SQL Server error log may identify the specific error. | Microsoft.SQLServer.2016.An_error_occurred_in_the_SQL_Server_Service_Broker_or_Database_Mirroring_transport_manager_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 9643 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: An error occurred in the timer event cache | An error occurred in the SQL Server Service Broker transport layer timer event cache. The Windows application log or SQL Server error log may identify the specific error. | Microsoft.SQLServer.2016.An_error_occurred_in_the_timer_event_cache_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 9646 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: An error occurred while processing SQL Server Service Broker mirroring routes | The rule triggers an alert when an error occurres while processing SQL Server Service Broker mirroring routes | Microsoft.SQLServer.2016.An_error_occurred_while_processing_SQL_Server_Service_Broker_mirroring_routes_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 9789 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: An error occurred while reading the log for database | This error indicates a failure while processing the transaction log during rollback, recovery, or replication. | Microsoft.SQLServer.2016.An_error_occurred_while_processing_the_log_for_database_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 9004 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | High | True | Application |
| MSSQL 2016: A SNI call failed during a Service Broker/Database Mirroring transport operation | The rule triggers an alert when a SNI call failes during a Service Broker/Database Mirroring transport operation. Note: This rule is disabled by default. Please use overrides to enable it when necessary. | Microsoft.SQLServer.2016.An_SNI_call_failed_during_a_Service_Broker_Database_Mirroring_transport_operation_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | False | | | 0 | 8471 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: An SQL Server Service Broker dialog detected an error | The rule triggers an alert when a SQL Server Service Broker dialog detects an error | Microsoft.SQLServer.2016.An_SQL_Server_Service_Broker_dialog_caught_an_error_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 9736 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: AppDomain failed to unload with error code | The rule triggers an application domain fails to unload because of some error. The Windows Application log may contain an information about the original error code and other diagnostic details | Microsoft.SQLServer.2016.AppDomain_failed_to_unload_with_error_code_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 6291 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Attempt to fetch logical page that belongs to different object | This error occurs when SQL Server detects that the allocation unit as stored on a database page does match the allocation unit associated with a specific operation, such as running a SELECT statement against a table. | Microsoft.SQLServer.2016.Attempt_to_fetch_logical_page_that_belongs_to_different_object_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 605 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | High | True | Application |
| MSSQL 2016: Could not use Address Windowing Extensions because 'lock pages in memory' privilege was not granted | The rule triggers an alert when SQL Server cannot use Address Windowing Extensions because 'lock pages in memory' because privilege was not granted. | Microsoft.SQLServer.2016.AWE__Could_not_use_Address_Windowing_Extensions_because__lock_pages_in_memory__privilege_was_not_granted_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 17179 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: A default full-text catalog does not exist in the database or user does not have permission to perform this action | The full-text catalog does not exist, or the user does not have the appropriate permission to create a full-text index in the catalog. | Microsoft.SQLServer.2016.A_default_full_text_catalog_does_not_exist_in_the_database_or_user_does_not_have_permission_to_perform_this_action_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 9967 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: A fatal error occurred in .NET Framework runtime | The rule triggers an alert when the .NET Framework shuts down due to an error. | Microsoft.SQLServer.2016.A_fatal_error_occurred_in_.NET_Framework_runtime_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 6536 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: A security (SSPI) error occurred when connecting to another Service Broker or Database Mirroring host | When Service Broker transport security uses SSPI, the service account for the remote database must have CONNECT permission in master database. Remote SQL Server instance should allow Windows Authentication for the account being used by remote host. There are no requirements for the login to have other permissions or to own objects in any database. | Microsoft.SQLServer.2016.A_security__SSPI__error_occurred_when_connecting_to_another_Service_Broker_or_Database_Mirroring_host_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 9649 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: A SQL job failed to complete successfully | A SQL Server Agent Job Failed. The SQL Server Agent is responsible for running SQL Server tasks scheduled to occur at specific times or intervals as well as detecting specific conditions for which administrators have defined an action, such as alerting someone through pages or e-mail, or a task that will address the conditions. The SQL Server Agent is also used for running replication tasks defined by administrators. Note: This rule is disabled by default. Please use overrides to enable it when necessary. | Microsoft.SQLServer.2016.A_SQL_job_failed_to_complete_successfully_1_5_Rule | Microsoft.SQLServer.2016.Agent | EventCollection | False | | | 0 | 0 | | True | Error | Normal | True | Application |
| MSSQL 2016: A SQL Server Service Broker conversation has been closed due to an error | The rule triggers an alert when a SQL Server Service Broker conversation has been closed due to an error. | Microsoft.SQLServer.2016.A_SQL_Server_Service_Broker_conversation_closed_due_to_an_error_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 9761 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: SQL Server Service Broker cryptographic operation failed | The rule triggers an alert when SQL Server Service Broker cryptographic operation failes. | Microsoft.SQLServer.2016.A_SQL_Server_Service_Broker_cryptographic_operation_failed_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 9641 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: A SQL Server Service Broker procedure output results | A stored procedure, which was internally activated by SQL Server Service Broker, output results. Internal procedures should not output results. The event in the Windows application log contains the procedure name, the queue name, and the output results. The event is logged as MSSQLSERVER event ID 9724. Note: This rule is disabled by default. Please use overrides to enable it when necessary. | Microsoft.SQLServer.2016.A_SQL_Server_Service_Broker_procedure_output_results_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | False | | | 0 | 9724 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Information | Low | True | Application |
| MSSQL 2016: Backup device failed - Operating system error | This message indicates that the operating system was unable to open or close a backup device (disk, tape, or pipe) specified as part of a BACKUP or RESTORE command. For more information on backup devices, refer to the Books Online topics, "Backup Devices" and "BACKUP." | Microsoft.SQLServer.2016.Backup_device_failed___Operating_system_error_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 18204 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Buffer Cache Hit Ratio | Collects the Windows "Buffer Cache Hit Ratio" performance counter for each instance of SQL 2016 DB Engine. | Microsoft.SQLServer.2016.BufferCacheHitRatio | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Buffer Manager | Buffer cache hit ratio | 900 | 0 | | False | | | True | |
| MSSQL 2016: Cannot determine the service account for SQL Server instance | This error occurs when a Transact-SQL statement contains mismatched single or double quotes. The SET QUOTED_IDENTIFIER setting will determine which combinations of single and double quotations marks are valid. For more information about SET QUOTED_IDENTIFIER, see "SET QUOTED_IDENTIFIER" in Books Online. | Microsoft.SQLServer.2016.Cannot_determine_the_service_account_for_SQL_Server_instance_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 14353 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Cannot open backup device. | One or more of the files specified in a BACKUP or RESTORE command could not be opened. The potential reasons for this include: | Microsoft.SQLServer.2016.Cannot_open_backup_device.__1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 3201 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Cannot open user default database. Login failed | When a client connects to a SQL Server instance without specifying a database context, the default database defined for its login is used. If that database is unavailable for any reason, the above message appears. | Microsoft.SQLServer.2016.Cannot_open_user_default_database._Login_failed_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 4064 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Cannot recover the master database. Exiting. | The master database is not in a recoverable state. | Microsoft.SQLServer.2016.Cannot_recover_the_master_database._Exiting_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 3417 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Cannot start service broker activation manager | The rule triggers an alert when service broker fails to start activation manager. | Microsoft.SQLServer.2016.Cannot_start_service_broker_activation_manager_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 9701 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Cannot start service broker manager | The rule triggers an alert when SQL Server cannot start service broker manager. | Microsoft.SQLServer.2016.Cannot_start_service_broker_manager_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 9694 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Cannot start service broker manager due to operating system error | The rule triggers an alert when SQL Server cannot start service broker manager due to operating system error. | Microsoft.SQLServer.2016.Cannot_start_service_broker_manager_due_to_operating_system_error_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 28002 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Cannot start service broker security manager | Service Broker security manger could not start. | Microsoft.SQLServer.2016.Cannot_start_service_broker_security_manager_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 9698 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Cannot start SQL Server Service Broker on a database | The rule triggers an alert when SQL Server cannot start Service Broker on a database. | Microsoft.SQLServer.2016.Cannot_start_SQL_Server_Service_Broker_on_Database_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 9697 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: CHECKTABLE processing of object encountered page twice. Possible internal error or allocation fault | Page P_ID was encountered twice during the course of the scan. | Microsoft.SQLServer.2016.CHECKTABLE_processing_of_object_encountered_page_twice._Possible_internal_error_or_allocation_fault_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8973 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: CHECKTABLE terminated. A failure was detected while collecting facts. | Possibly tempdb out of space or a system table is inconsistent. Check previous errors. | Microsoft.SQLServer.2016.CHECKTABLE_terminated._A_failure_was_detected_while_collecting_facts._Possibly_tempdb_out_of_space_or_a_system_table_is_inconsistent._Check_previous_errors_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8921 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Checksum failure while page in cache | It is detected that a database page has been unexpectedly modified while in cache (by verifying the page checksum). | Microsoft.SQLServer.2016.Check_sum_failure_while_page_in_cache_id832 | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 832 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | High | True | Application |
| MSSQL 2016: Memory-Optimized Data Filegroup container free space (MB) | Collects the amount of free space available for the Memory-Optimized Data Filegroup container (in Megabytes). | Microsoft.SQLServer.2016.CollectionRule.Container.SpaceFreeMB | Microsoft.SQLServer.2016.Container | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: Memory-Optimized Data Filegroup container free space (\%) | Collects the amount of free space available in the Memory-Optimized Data Filegroup container, expressed as percentage of the sum of disk free space and the size of data stored in the Memory-Optimized Data Filegroup container. | Microsoft.SQLServer.2016.CollectionRule.Container.SpaceFreePercent | Microsoft.SQLServer.2016.Container | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: HTTP Storage: Avg. Bytes/Read | Collects the Windows "HTTP Storage:Avg. Bytes/Read" performance counter for SQL DB Engine that monitor Windows Azure Storage account. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.HTTPStorageAvgBytesPerRead | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:HTTP Storage | Avg. Bytes/Read | 900 | 0 | | False | | | True | |
| MSSQL 2016: HTTP Storage: Avg. Bytes/Transfer | Collects the Windows "HTTP Storage:Avg. Bytes/Transfer" performance counter for SQL DB Engine that monitor Windows Azure Storage account. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.HTTPStorageAvgBytesPerTransfer | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:HTTP Storage | Avg. Bytes/Transfer | 900 | 0 | | False | | | True | |
| MSSQL 2016: HTTP Storage: Avg. Bytes/Write | Collects the Windows "HTTP Storage:Avg. Bytes/Write" performance counter for SQL DB Engine that monitor Windows Azure Storage account. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.HTTPStorageAvgBytesPerWrite | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:HTTP Storage | Avg. Bytes/Write | 900 | 0 | | False | | | True | |
| MSSQL 2016: HTTP Storage: Avg. microsec/Read | Collects the Windows "HTTP Storage:Avg. microsec/Read" performance counter for SQL DB Engine that monitor Windows Azure Storage account. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.HTTPStorageAvgMicrosecPerRead | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:HTTP Storage | Avg. microsec/Read | 900 | 0 | | False | | | True | |
| MSSQL 2016: HTTP Storage: Avg. microsec/Read Comp | Collects the Windows "HTTP Storage:Avg. microsec/Read Comp" performance counter for SQL DB Engine that monitor Windows Azure Storage account. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.HTTPStorageAvgMicrosecPerReadComp | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:HTTP Storage | Avg. microsec/Read Comp | 900 | 0 | | False | | | True | |
| MSSQL 2016: HTTP Storage: Avg. microsec/Transfer | Collects the Windows "HTTP Storage:Avg. microsec/Transfer" performance counter for SQL DB Engine that monitor Windows Azure Storage account. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.HTTPStorageAvgMicrosecPerTransfer | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:HTTP Storage | Avg. microsec/Transfer | 900 | 0 | | False | | | True | |
| MSSQL 2016: HTTP Storage: Avg. microsec/Write | Collects the Windows "HTTP Storage:Avg. microsec/Write" performance counter for SQL DB Engine that monitor Windows Azure Storage account. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.HTTPStorageAvgMicrosecPerWrite | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:HTTP Storage | Avg. microsec/Write | 900 | 0 | | False | | | True | |
| MSSQL 2016: HTTP Storage: Avg. microsec/Write Comp | Collects the Windows "HTTP Storage:Avg. microsec/Write Comp" performance counter for SQL DB Engine that monitor Windows Azure Storage account. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.HTTPStorageAvgMicrosecPerWriteComp | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:HTTP Storage | Avg. microsec/Write Comp | 900 | 0 | | False | | | True | |
| MSSQL 2016: HTTP Storage: HTTP Storage IO failed/sec | Collects the Windows "HTTP Storage:HTTP Storage IO failed/sec" performance counter for SQL DB Engine that monitor Windows Azure Storage account. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.HTTPStorageHTTPStorageIOFailedPerSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:HTTP Storage | HTTP Storage IO failed/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: HTTP Storage: HTTP Storage IO retry/sec | Collects the Windows "HTTP Storage:HTTP Storage IO retry/sec" performance counter for SQL DB Engine that monitor Windows Azure Storage account. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.HTTPStorageHTTPStorageIORetryPerSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:HTTP Storage | HTTP Storage IO retry/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: HTTP Storage: Outstanding HTTP Storage IO | Collects the Windows "HTTP Storage:Outstanding HTTP Storage IO" performance counter for SQL DB Engine that monitor Windows Azure Storage account. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.HTTPStorageOutstandingHTTPStorageIO | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:HTTP Storage | Outstanding HTTP Storage IO | 900 | 0 | | False | | | True | |
| MSSQL 2016: HTTP Storage: Read Bytes/Sec | Collects the Windows "HTTP Storage:Read Bytes/Sec" performance counter for SQL DB Engine that monitor Windows Azure Storage account. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.HTTPStorageReadBytesPerSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:HTTP Storage | Read Bytes/Sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: HTTP Storage: Reads/sec | Collects the Windows "HTTP Storage:Reads/sec" performance counter for SQL DB Engine that monitor Windows Azure Storage account. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.HTTPStorageReadsPerSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:HTTP Storage | Reads/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: HTTP Storage: Total Bytes/sec | Collects the Windows "HTTP Storage:Total Bytes/sec" performance counter for SQL DB Engine that monitor Windows Azure Storage account. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.HTTPStorageTotalBytesPerSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:HTTP Storage | Total Bytes/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: HTTP Storage: Transfers/sec | Collects the Windows "HTTP Storage:Transfers/sec" performance counter for SQL DB Engine that monitor Windows Azure Storage account. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.HTTPStorageTransfersPerSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:HTTP Storage | Transfers/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: HTTP Storage: Write Bytes/Sec | Collects the Windows "HTTP Storage:Write Bytes/Sec" performance counter for SQL DB Engine that monitor Windows Azure Storage account. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.HTTPStorageWriteBytesPerSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:HTTP Storage | Write Bytes/Sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: HTTP Storage: Writes/Sec | Collects the Windows "HTTP Storage:Writes/Sec" performance counter for SQL DB Engine that monitor Windows Azure Storage account. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.HTTPStorageWritesPerSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:HTTP Storage | Writes/Sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Avg Transaction Segment Large Data Size | Collects the Windows "Avg Transaction Segment Large Data Size" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPAvgTransactionSegmentLargeDataSize | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | Avg Transaction Segment Large Data Size | 900 | 0 | | False | | | True | |
| MSSQL 2016: Avg Transaction Segment Size | Collects the Windows "Avg Transaction Segment Size" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPAvgTransactionSegmentSize | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | Avg Transaction Segment Size | 900 | 0 | | False | | | True | |
| MSSQL 2016: Cascading aborts/sec | Collects the Windows "Cascading aborts/sec" performance counter for XTP engine transactions in SQL Server. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPCascadingAbortsSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Transactions | Cascading aborts/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Checkpoints Closed | Collects the Windows "Checkpoints Closed" performance counter for the XTP engine's storage subsystem. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPCheckpointsClosed | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Storage | Checkpoints Closed | 900 | 0 | | False | | | True | |
| MSSQL 2016: Checkpoints Completed | Collects the Windows "Checkpoints Completed" performance counter for the XTP engine's storage subsystem. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPCheckpointsCompleted | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Storage | Checkpoints Completed | 900 | 0 | | False | | | True | |
| MSSQL 2016: Commit dependencies taken/sec | Collects the Windows "Commit dependencies taken/sec" performance counter for XTP engine transactions in SQL Server. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPCommitDependenciesTakenSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Transactions | Commit dependencies taken/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Core Merges Completed | Collects the Windows "Core Merges Completed" performance counter for the XTP engine's storage subsystem. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPCoreMergesCompleted | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Storage | Core Merges Completed | 900 | 0 | | False | | | True | |
| MSSQL 2016: Cursor deletes/sec | Collects the Windows "Cursor deletes/sec" performance counter for internal XTP engine cursors. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPCursorDeletesSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Cursors | Cursor deletes/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Cursor inserts/sec | Collects the Windows "Cursor inserts/sec" performance counter for internal XTP engine cursors. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPCursorInsertsSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Cursors | Cursor inserts/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Cursor scans started/sec | Collects the Windows "Cursor scans started/sec" performance counter for internal XTP engine cursors. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPCursorScansStartedSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Cursors | Cursor scans started/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Cursor unique violations/sec | Collects the Windows "Cursor unique violations/sec" performance counter for internal XTP engine cursors. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPCursorUniqueViolationsSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Cursors | Cursor unique violations/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Cursor updates/sec | Collects the Windows "Cursor updates/sec" performance counter for internal XTP engine cursors. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPCursorUpdatesSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Cursors | Cursor updates/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Cursor write conflicts/sec | Collects the Windows "Cursor write conflicts/sec" performance counter for internal XTP engine cursors. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPCursorWriteConflictsSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Cursors | Cursor write conflicts/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Dusty corner scan retries/sec (GC-issued) | Collects the Windows "Dusty corner scan retries/sec (GC-issued)" performance counter for the XTP engine's garbage collector. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPDustyCornerScanRetriesSecGcIssued | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Garbage Collection | Dusty corner scan retries/sec (GC-issued) | 900 | 0 | | False | | | True | |
| MSSQL 2016: Dusty corner scan retries/sec (Phantom-issued) | Collects the Windows "Dusty corner scan retries/sec (Phantom-issued)" performance counter for the XTP engine's phantom processing subsystem. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPDustyCornerScanRetriesSecPhantomIssued | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Phantom Processor | Dusty corner scan retries/sec (Phantom-issued) | 900 | 0 | | False | | | True | |
| MSSQL 2016: Dusty corner scan retries/sec (user-issued) | Collects the Windows "Dusty corner scan retries/sec (user-issued)" performance counter for internal XTP engine cursors. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPDustyCornerScanRetriesSecUserIssued | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Cursors | Dusty corner scan retries/sec (user-issued) | 900 | 0 | | False | | | True | |
| MSSQL 2016: Expired rows removed/sec | Collects the Windows "Expired rows removed/sec" performance counter for internal XTP engine cursors. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPExpiredRowsRemovedSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Cursors | Expired rows removed/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Expired rows touched/sec | Collects the Windows "Expired rows touched/sec" performance counter for internal XTP engine cursors. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPExpiredRowsTouchedSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Cursors | Expired rows touched/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Flush Thread 256K Queue Depth | Collects the Windows "Flush Thread 256K Queue Depth" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPFlushThread256KQueueDepth | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | Flush Thread 256K Queue Depth | 900 | 0 | | False | | | True | |
| MSSQL 2016: Flush Thread 4K Queue Depth | Collects the Windows "Flush Thread 4K Queue Depth" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPFlushThread4KQueueDepth | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | Flush Thread 4K Queue Depth | 900 | 0 | | False | | | True | |
| MSSQL 2016: Flush Thread 64K Queue Depth | Collects the Windows "Flush Thread 64K Queue Depth" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPFlushThread64KQueueDepth | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | Flush Thread 64K Queue Depth | 900 | 0 | | False | | | True | |
| MSSQL 2016: Flush Thread Frozen IOs/sec (256K) | Collects the Windows "Flush Thread Frozen IOs/sec (256K)" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPFlushThreadFrozenIosSec256K | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | Flush Thread Frozen IOs/sec (256K) | 900 | 0 | | False | | | True | |
| MSSQL 2016: Flush Thread Frozen IOs/sec (4K) | Collects the Windows "Flush Thread Frozen IOs/sec (4K)" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPFlushThreadFrozenIosSec4K | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | Flush Thread Frozen IOs/sec (4K) | 900 | 0 | | False | | | True | |
| MSSQL 2016: Flush Thread Frozen IOs/sec (64K) | Collects the Windows "Flush Thread Frozen IOs/sec (64K)" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPFlushThreadFrozenIosSec64K | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | Flush Thread Frozen IOs/sec (64K) | 900 | 0 | | False | | | True | |
| MSSQL 2016: Insufficient Credits Waits/sec | Collects the Windows "Insufficient Credits Waits/sec" performance counter for the XTP IO Rate Governor. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPInsufficientCreditsWaitsSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP IO Governor | Insufficient Credits Waits/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Io Issued/sec | Collects the Windows "Io Issued/sec" performance counter for the XTP IO Rate Governor. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPIoIssuedSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP IO Governor | Io Issued/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: IoPagePool256K Free List Count | Collects the Windows "IoPagePool256K Free List Count" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPIopagepool256kFreeListCount | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | IoPagePool256K Free List Count | 900 | 0 | | False | | | True | |
| MSSQL 2016: IoPagePool256K Total Allocated | Collects the Windows "IoPagePool256K Total Allocated" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPIopagepool256kTotalAllocated | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | IoPagePool256K Total Allocated | 900 | 0 | | False | | | True | |
| MSSQL 2016: IoPagePool4K Free List Count | Collects the Windows "IoPagePool4K Free List Count" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPIopagepool4kFreeListCount | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | IoPagePool4K Free List Count | 900 | 0 | | False | | | True | |
| MSSQL 2016: IoPagePool4K Total Allocated | Collects the Windows "IoPagePool4K Total Allocated" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPIopagepool4kTotalAllocated | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | IoPagePool4K Total Allocated | 900 | 0 | | False | | | True | |
| MSSQL 2016: IoPagePool64K Free List Count | Collects the Windows "IoPagePool64K Free List Count" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPIopagepool64kFreeListCount | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | IoPagePool64K Free List Count | 900 | 0 | | False | | | True | |
| MSSQL 2016: IoPagePool64K Total Allocated | Collects the Windows "IoPagePool64K Total Allocated" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPIopagepool64kTotalAllocated | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | IoPagePool64K Total Allocated | 900 | 0 | | False | | | True | |
| MSSQL 2016: Log Blocks/sec | Collects the Windows "Log Blocks/sec" performance counter for the XTP IO Rate Governor. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPLogBlocksSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP IO Governor | Log Blocks/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Log bytes written/sec | Collects the Windows "Log bytes written/sec" performance counter for XTP transaction logging in SQL Server. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPLogBytesWrittenSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Transaction Log | Log bytes written/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Log records written/sec | Collects the Windows "Log records written/sec" performance counter for XTP transaction logging in SQL Server. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPLogRecordsWrittenSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Transaction Log | Log records written/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Main GC work items/sec | Collects the Windows "Main GC work items/sec" performance counter for the XTP engine's garbage collector. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPMainGcWorkItemsSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Garbage Collection | Main GC work items/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Merge Policy Evaluations | Collects the Windows "Merge Policy Evaluations" performance counter for the XTP engine's storage subsystem. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPMergePolicyEvaluations | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Storage | Merge Policy Evaluations | 900 | 0 | | False | | | True | |
| MSSQL 2016: Merge Requests Outstanding | Collects the Windows "Merge Requests Outstanding" performance counter for the XTP engine's storage subsystem. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPMergeRequestsOutstanding | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Storage | Merge Requests Outstanding | 900 | 0 | | False | | | True | |
| MSSQL 2016: Merges Abandoned | Collects the Windows "Merges Abandoned" performance counter for the XTP engine's storage subsystem. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPMergesAbandoned | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Storage | Merges Abandoned | 900 | 0 | | False | | | True | |
| MSSQL 2016: Merges Installed | Collects the Windows "Merges Installed" performance counter for the XTP engine's storage subsystem. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPMergesInstalled | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Storage | Merges Installed | 900 | 0 | | False | | | True | |
| MSSQL 2016: Missed Credit Slots | Collects the Windows "Missed Credit Slots" performance counter for the XTP IO Rate Governor. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPMissedCreditSlots | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP IO Governor | Missed Credit Slots | 900 | 0 | | False | | | True | |
| MSSQL 2016: MtLog 256K Expand Count | Collects the Windows "MtLog 256K Expand Count" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPMtlog256KExpandCount | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | MtLog 256K Expand Count | 900 | 0 | | False | | | True | |
| MSSQL 2016: MtLog 256K IOs Outstanding | Collects the Windows "MtLog 256K IOs Outstanding" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPMtlog256KIosOutstanding | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | MtLog 256K IOs Outstanding | 900 | 0 | | False | | | True | |
| MSSQL 2016: MtLog 256K Page Fill \%/Page Flushed | Collects the Windows "MtLog 256K Page Fill \%/Page Flushed" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPMtlog256KPageFillPageFlushed | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | MtLog 256K Page Fill \%/Page Flushed | 900 | 0 | | False | | | True | |
| MSSQL 2016: MtLog 256K Write Bytes/sec | Collects the Windows "MtLog 256K Write Bytes/sec" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPMtlog256KWriteBytesSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | MtLog 256K Write Bytes/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: MtLog 4K Expand Count | Collects the Windows "MtLog 4K Expand Count" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPMtlog4KExpandCount | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | MtLog 4K Expand Count | 900 | 0 | | False | | | True | |
| MSSQL 2016: MtLog 4K IOs Outstanding | Collects the Windows "MtLog 4K IOs Outstanding" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPMtlog4KIosOutstanding | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | MtLog 4K IOs Outstanding | 900 | 0 | | False | | | True | |
| MSSQL 2016: MtLog 4K Page Fill \%/Page Flushed | Collects the Windows "MtLog 4K Page Fill \%/Page Flushed" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPMtlog4KPageFillPageFlushed | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | MtLog 4K Page Fill \%/Page Flushed | 900 | 0 | | False | | | True | |
| MSSQL 2016: MtLog 4K Write Bytes/sec | Collects the Windows "MtLog 4K Write Bytes/sec" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPMtlog4KWriteBytesSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | MtLog 4K Write Bytes/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: MtLog 64K Expand Count | Collects the Windows "MtLog 64K Expand Count" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPMtlog64KExpandCount | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | MtLog 64K Expand Count | 900 | 0 | | False | | | True | |
| MSSQL 2016: MtLog 64K IOs Outstanding | Collects the Windows "MtLog 64K IOs Outstanding" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPMtlog64KIosOutstanding | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | MtLog 64K IOs Outstanding | 900 | 0 | | False | | | True | |
| MSSQL 2016: MtLog 64K Page Fill \%/Page Flushed | Collects the Windows "MtLog 64K Page Fill \%/Page Flushed" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPMtlog64KPageFillPageFlushed | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | MtLog 64K Page Fill \%/Page Flushed | 900 | 0 | | False | | | True | |
| MSSQL 2016: MtLog 64K Write Bytes/sec | Collects the Windows "MtLog 64K Write Bytes/sec" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPMtlog64KWriteBytesSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | MtLog 64K Write Bytes/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Num Merges | Collects the Windows "Num Merges" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPNumMerges | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | Num Merges | 900 | 0 | | False | | | True | |
| MSSQL 2016: Num Merges/sec | Collects the Windows "Num Merges/sec" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPNumMergesSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | Num Merges/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Num Serializations | Collects the Windows "Num Serializations" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPNumSerializations | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | Num Serializations | 900 | 0 | | False | | | True | |
| MSSQL 2016: Num Serializations/sec | Collects the Windows "Num Serializations/sec" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPNumSerializationsSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | Num Serializations/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Parallel GC work item/sec | Collects the Windows "Parallel GC work item/sec" performance counter for the XTP engine's garbage collector. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPParallelGcWorkItemSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Garbage Collection | Parallel GC work item/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Phantom expired rows removed/sec | Collects the Windows "Phantom expired rows removed/sec" performance counter for the XTP engine's phantom processing subsystem. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPPhantomExpiredRowsRemovedSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Phantom Processor | Phantom expired rows removed/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Phantom expired rows touched/sec | Collects the Windows "Phantom expired rows touched/sec" performance counter for the XTP engine's phantom processing subsystem. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPPhantomExpiredRowsTouchedSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Phantom Processor | Phantom expired rows touched/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Phantom expiring rows touched/sec | Collects the Windows "Phantom expiring rows touched/sec" performance counter for the XTP engine's phantom processing subsystem. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPPhantomExpiringRowsTouchedSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Phantom Processor | Phantom expiring rows touched/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Phantom rows touched/sec | Collects the Windows "Phantom rows touched/sec" performance counter for the XTP engine's phantom processing subsystem. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPPhantomRowsTouchedSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Phantom Processor | Phantom rows touched/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Phantom scans started/sec | Collects the Windows "Phantom scans started/sec" performance counter for the XTP engine's phantom processing subsystem. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPPhantomScansStartedSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Phantom Processor | Phantom scans started/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Read-only transactions prepared/sec | Collects the Windows "Read-only transactions prepared/sec" performance counter for XTP engine transactions in SQL Server. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPReadOnlyTransactionsPreparedSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Transactions | Read-only transactions prepared/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Rows processed/sec | Collects the Windows "Rows processed/sec" performance counter for the XTP engine's garbage collector. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPRowsProcessedSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Garbage Collection | Rows processed/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Rows processed/sec (first in bucket) | Collects the Windows "Rows processed/sec (first in bucket)" performance counter for the XTP engine's garbage collector. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPRowsProcessedSecFirstInBucket | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Garbage Collection | Rows processed/sec (first in bucket) | 900 | 0 | | False | | | True | |
| MSSQL 2016: Rows processed/sec (first in bucket and removed) | Collects the Windows "Rows processed/sec (first in bucket and removed)" performance counter for the XTP engine's garbage collector. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPRowsProcessedSecFirstInBucketAndRemoved | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Garbage Collection | Rows processed/sec (first in bucket and removed) | 900 | 0 | | False | | | True | |
| MSSQL 2016: Rows processed/sec (marked for unlink) | Collects the Windows "Rows processed/sec (marked for unlink)" performance counter for the XTP engine's garbage collector. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPRowsProcessedSecMarkedForUnlink | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Garbage Collection | Rows processed/sec (marked for unlink) | 900 | 0 | | False | | | True | |
| MSSQL 2016: Rows processed/sec (no sweep needed) | Collects the Windows "Rows processed/sec (no sweep needed)" performance counter for the XTP engine's garbage collector. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPRowsProcessedSecNoSweepNeeded | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Garbage Collection | Rows processed/sec (no sweep needed) | 900 | 0 | | False | | | True | |
| MSSQL 2016: Rows returned/sec | Collects the Windows "Rows returned/sec" performance counter for internal XTP engine cursors. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPRowsReturnedSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Cursors | Rows returned/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Rows touched/sec | Collects the Windows "Rows touched/sec" performance counter for internal XTP engine cursors. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPRowsTouchedSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Cursors | Rows touched/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Save point refreshes/sec | Collects the Windows "Save point refreshes/sec" performance counter for XTP engine transactions in SQL Server. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPSavePointRefreshesSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Transactions | Save point refreshes/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Save point rollbacks/sec | Collects the Windows "Save point rollbacks/sec" performance counter for XTP engine transactions in SQL Server. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPSavePointRollbacksSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Transactions | Save point rollbacks/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Save points created/sec | Collects the Windows "Save points created/sec" performance counter for XTP engine transactions in SQL Server. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPSavePointsCreatedSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Transactions | Save points created/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Stale Rate Object Waits/sec | Collects the Windows "Stale Rate Object Waits/sec" performance counter for the XTP IO Rate Governor. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPStaleRateObjectWaitsSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP IO Governor | Stale Rate Object Waits/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Sweep expired rows removed/sec | Collects the Windows "Sweep expired rows removed/sec" performance counter for the XTP engine's garbage collector. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPSweepExpiredRowsRemovedSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Garbage Collection | Sweep expired rows removed/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Sweep expired rows touched/sec | Collects the Windows "Sweep expired rows touched/sec" performance counter for the XTP engine's garbage collector. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPSweepExpiredRowsTouchedSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Garbage Collection | Sweep expired rows touched/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Sweep expiring rows touched/sec | Collects the Windows "Sweep expiring rows touched/sec" performance counter for the XTP engine's garbage collector. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPSweepExpiringRowsTouchedSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Garbage Collection | Sweep expiring rows touched/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Sweep rows touched/sec | Collects the Windows "Sweep rows touched/sec" performance counter for the XTP engine's garbage collector. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPSweepRowsTouchedSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Garbage Collection | Sweep rows touched/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Sweep scans started/sec | Collects the Windows "Sweep scans started/sec" performance counter for the XTP engine's garbage collector. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPSweepScansStartedSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Garbage Collection | Sweep scans started/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Tail Cache Page Count | Collects the Windows "Tail Cache Page Count" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPTailCachePageCount | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | Tail Cache Page Count | 900 | 0 | | False | | | True | |
| MSSQL 2016: Tail Cache Page Count Peak | Collects the Windows "Tail Cache Page Count Peak" performance counter for SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPTailCachePageCountPeak | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Databases | Tail Cache Page Count Peak | 900 | 0 | | False | | | True | |
| MSSQL 2016: Tentatively-deleted rows touched/sec | Collects the Windows "Tentatively-deleted rows touched/sec" performance counter for internal XTP engine cursors. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPTentativelyDeletedRowsTouchedSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Cursors | Tentatively-deleted rows touched/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Total Files Merged | Collects the Windows "Total Files Merged" performance counter for the XTP engine's storage subsystem. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPTotalFilesMerged | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Storage | Total Files Merged | 900 | 0 | | False | | | True | |
| MSSQL 2016: Total Rate Objects Published | Collects the Windows "Total Rate Objects Published" performance counter for the XTP IO Rate Governor. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPTotalRateObjectsPublished | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP IO Governor | Total Rate Objects Published | 900 | 0 | | False | | | True | |
| MSSQL 2016: Transactions aborted by user/sec | Collects the Windows "Transactions aborted by user/sec" performance counter for XTP engine transactions in SQL Server. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPTransactionsAbortedByUserSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Transactions | Transactions aborted by user/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Transactions aborted/sec | Collects the Windows "Transactions aborted/sec" performance counter for XTP engine transactions in SQL Server. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPTransactionsAbortedSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Transactions | Transactions aborted/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Transactions created/sec | Collects the Windows "Transactions created/sec" performance counter for XTP engine transactions in SQL Server. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPTransactionsCreatedSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Transactions | Transactions created/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Transaction validation failures/sec | Collects the Windows "Transaction validation failures/sec" performance counter for XTP engine transactions in SQL Server. | Microsoft.SQLServer.2016.CollectionRule.DBEngine.XTPTransactionValidationFailuresSec | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | SQL Server 2016 XTP Transactions | Transaction validation failures/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Active Checkpoint File Pairs | Collects the number of active checkpoint file pairs in Memory-Optimized Data Filegroup. | Microsoft.SQLServer.2016.CollectionRule.DBFileGroupFx.CheckpointFile.Active | Microsoft.SQLServer.2016.DBFileGroupFx | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: Merge Target Checkpoint File Pairs | Collects the number of merge target checkpoint file pairs in Memory-Optimized Data Filegroup. | Microsoft.SQLServer.2016.CollectionRule.DBFileGroupFx.CheckpointFile.MergeTarget | Microsoft.SQLServer.2016.DBFileGroupFx | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: Precreated Checkpoint Files | Collects the number of Precreated Checkpoint Files in Memory-Optimized Data Filegroup. | Microsoft.SQLServer.2016.CollectionRule.DBFileGroupFx.CheckpointFile.Precreated | Microsoft.SQLServer.2016.DBFileGroupFx | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: Checkpoint File Pairs Waiting For Log Truncation | Collects the number of Checkpoint Files Waiting For Log Truncation in Memory-Optimized Data Filegroup. | Microsoft.SQLServer.2016.CollectionRule.DBFileGroupFx.CheckpointFile.Stale | Microsoft.SQLServer.2016.DBFileGroupFx | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: Checkpoint File Pairs Under Construction | Collects the number of checkpoint file pairs under construction in Memory-Optimized Data Filegroup. | Microsoft.SQLServer.2016.CollectionRule.DBFileGroupFx.CheckpointFile.UnderConstruction | Microsoft.SQLServer.2016.DBFileGroupFx | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| [Deprecated] MSSQL 2016: Memory-Optimized Data Garbage Collection Fill Factor (\%) | Collects Garbage Collection Fill Factor (an amount of space used by active rows in Memory-Optimized Data files, expressed as a percentage of the size of data files) for Memory-Optimized Data Filegroup. Note: This rule is disabled by default. Please use overrides to enable it when necessary.
This rule is considered to be obsolete in this Management Pack. | Microsoft.SQLServer.2016.CollectionRule.DBFileGroupFx.GarbageCollectionFillFactor | Microsoft.SQLServer.2016.DBFileGroupFx | PerformanceCollection | False | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: Memory Used By Indexes (MB) | Collects the amount of memory allocated for indexes defined for memory-optimized tables in the given SQL Server 2016 Database. | Microsoft.SQLServer.2016.CollectionRule.DBFileGroupFx.IndexesUsedMemoryMB | Microsoft.SQLServer.2016.DBFileGroupFx | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB Memory-Optimized Data Filegroup Free Space Total (MB) | Collects the amount of free space available across all containers in the Memory-Optimized Data Filegroup (in Megabytes). | Microsoft.SQLServer.2016.CollectionRule.DBFileGroupFx.SpaceFreeMegabytes | Microsoft.SQLServer.2016.DBFileGroupFx | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB Memory-Optimized Data Filegroup Free Space Total (\%) | Collects the amount of free space available across all containers in the Memory-Optimized Data Filegroup, expressed as percentage of the sum of disk free space and the size of data stored in the Memory-Optimized Data Filegroup. | Microsoft.SQLServer.2016.CollectionRule.DBFileGroupFx.SpaceFreePercent | Microsoft.SQLServer.2016.DBFileGroupFx | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: Memory Used By Tables (MB) | Collects the amount of memory allocated for memory-optimized tables in the given SQL Server 2016 Database. | Microsoft.SQLServer.2016.CollectionRule.DBFileGroupFx.TablesMemoryUsageMB | Microsoft.SQLServer.2016.DBFileGroupFx | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: XTP Controller DLC Latency/Fetch | Collects the Windows "XTP Controller DLC Latency/Fetch" performance counter for SQL 2016 Database with Memory-Optimized tables. | Microsoft.SQLServer.2016.CollectionRule.DBFileGroupFx.XTPControllerDLCLatencyFetch | Microsoft.SQLServer.2016.DBFileGroupFx | PerformanceCollection | True | $Target/Host/Host/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Databases | XTP Controller DLC Latency/Fetch | 900 | 0 | | False | | | True | |
| MSSQL 2016: XTP Controller DLC Peak Latency | Collects the Windows "XTP Controller DLC Peak Latency" performance counter for SQL 2016 Database with Memory-Optimized tables. | Microsoft.SQLServer.2016.CollectionRule.DBFileGroupFx.XTPControllerDLCPeakLatency | Microsoft.SQLServer.2016.DBFileGroupFx | PerformanceCollection | True | $Target/Host/Host/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Databases | XTP Controller DLC Peak Latency | 900 | 0 | | False | | | True | |
| MSSQL 2016: XTP Controller Log Processed/sec | Collects the Windows "XTP Controller Log Processed/sec" performance counter for SQL 2016 Database with Memory-Optimized tables. | Microsoft.SQLServer.2016.CollectionRule.DBFileGroupFx.XTPControllerLogProcessedSec | Microsoft.SQLServer.2016.DBFileGroupFx | PerformanceCollection | True | $Target/Host/Host/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Databases | XTP Controller Log Processed/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: XTP Memory Used (KB) | Collects the Windows "XTP Memory Used (KB)" performance counter for SQL 2016 Database with Memory-Optimized tables. | Microsoft.SQLServer.2016.CollectionRule.DBFileGroupFx.XTPMemoryUsedKB | Microsoft.SQLServer.2016.DBFileGroupFx | PerformanceCollection | True | $Target/Host/Host/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Databases | XTP Memory Used (KB) | 900 | 0 | | False | | | True | |
| MSSQL 2016: Number of query memory grants in the resource pool | Collects the Windows "Active Memory grant amount (KB)" performance counter for each resource pool of SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.ResourcePool.ActiveMemoryGrantAmountKB | Microsoft.SQLServer.2016.ResourcePool | PerformanceCollection | True | $Target/Host/Host/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Resource Pool Stats | Active Memory grant amount (KB) | 900 | 0 | | False | | | True | |
| MSSQL 2016: Total amount of granted memory in the resource pool (KB) | Collects the Windows "Active memory grants count" performance counter for each resource pool of SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.ResourcePool.ActiveMemoryGrantsCount | Microsoft.SQLServer.2016.ResourcePool | PerformanceCollection | True | $Target/Host/Host/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Resource Pool Stats | Active memory grants count | 900 | 0 | | False | | | True | |
| MSSQL 2016: Current memory target for cache memory (KB) | Collects the Windows "Cache memory target (KB)" performance counter for each resource pool of SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.ResourcePool.CacheMemoryTargetKB | Microsoft.SQLServer.2016.ResourcePool | PerformanceCollection | True | $Target/Host/Host/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Resource Pool Stats | Cache memory target (KB) | 900 | 0 | | False | | | True | |
| MSSQL 2016: Current memory target for query compile (KB) | Collects the Windows "Compile Memory Target (KB)" performance counter for each resource pool of SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.ResourcePool.CompileMemoryTargetKB | Microsoft.SQLServer.2016.ResourcePool | PerformanceCollection | True | $Target/Host/Host/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Resource Pool Stats | Compile Memory Target (KB) | 900 | 0 | | False | | | True | |
| MSSQL 2016: Maximum amount of memory the resource pool can have based on the settings and server state (KB) | Collects the Windows "Max memory (KB)" performance counter for each resource pool of SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.ResourcePool.MaxMemoryKB | Microsoft.SQLServer.2016.ResourcePool | PerformanceCollection | True | $Target/Host/Host/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Resource Pool Stats | Max memory (KB) | 900 | 0 | | False | | | True | |
| MSSQL 2016: Number of query memory grants per second occurring in the resource pool | Collects the Windows "Memory grants/sec" performance counter for each resource pool of SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.ResourcePool.MemoryGrantsSec | Microsoft.SQLServer.2016.ResourcePool | PerformanceCollection | True | $Target/Host/Host/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Resource Pool Stats | Memory grants/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Number of query memory grant timeouts per second occurring in the resource pool | Collects the Windows "Memory grant timeouts/sec" performance counter for each resource pool of SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.ResourcePool.MemoryGrantTimeoutsSec | Microsoft.SQLServer.2016.ResourcePool | PerformanceCollection | True | $Target/Host/Host/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Resource Pool Stats | Memory grant timeouts/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Number of queries waiting for memory grants in the resource pool. | Collects the Windows "Pending memory grants count" performance counter for each resource pool of SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.ResourcePool.PendingMemoryGrantsCount | Microsoft.SQLServer.2016.ResourcePool | PerformanceCollection | True | $Target/Host/Host/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Resource Pool Stats | Pending memory grants count | 900 | 0 | | False | | | True | |
| MSSQL 2016: Current memory target for query execution memory grant (KB) | Collects the Windows "Query exec memory target (KB)" performance counter for each resource pool of SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.ResourcePool.QueryExecMemoryTargetKB | Microsoft.SQLServer.2016.ResourcePool | PerformanceCollection | True | $Target/Host/Host/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Resource Pool Stats | Query exec memory target (KB) | 900 | 0 | | False | | | True | |
| MSSQL 2016: Target amount of memory the resource pool is trying to attain based on the settings and server state (KB) | Collects the Windows "Target memory (KB)" performance counter for each resource pool of SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.ResourcePool.TargetMemoryKB | Microsoft.SQLServer.2016.ResourcePool | PerformanceCollection | True | $Target/Host/Host/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Resource Pool Stats | Target memory (KB) | 900 | 0 | | False | | | True | |
| MSSQL 2016: Used amount of memory in the resource pool (KB) | Collects the Windows "Used memory (KB)" performance counter for each resource pool of SQL 2016 DB Engine. | Microsoft.SQLServer.2016.CollectionRule.ResourcePool.UsedMemoryKB | Microsoft.SQLServer.2016.ResourcePool | PerformanceCollection | True | $Target/Host/Host/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Resource Pool Stats | Used memory (KB) | 900 | 0 | | False | | | True | |
| MSSQL 2016: User Resource Pool Memory Consumption (MB) | Collects amount of memory used by the resource pool (in Megabytes). | Microsoft.SQLServer.2016.CollectionRule.UserResourcePool.MemoryConsumptionMB | Microsoft.SQLServer.2016.UserResourcePool | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: User Resource Pool Memory Consumption (\%) | Collects amount of memory used by the resource pool, expressed as a percentage of memory available for Memory-Optimized Data tables for the given Resource Pool. | Microsoft.SQLServer.2016.CollectionRule.UserResourcePool.MemoryConsumptionPercent | Microsoft.SQLServer.2016.UserResourcePool | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: Commit of internal MSDTC transaction failed | The rule triggers an error when COMMIT of internal MSDTC transaction failed | Microsoft.SQLServer.2016.Commit_of_internal_MSDTC_transaction_failed_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8520 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Common Language Runtime (CLR) not installed properly | This installation of the Common Language Runtime (CLR) is corrupted. The CLR is installed with the Microsoft .NET Framework. | Microsoft.SQLServer.2016.Common_Language_Runtime__CLR__not_installed_properly_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 6510 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Conflict table does not exist | This error occurs when you try to add or drop a column to a merge article, but the conflict table specified in sysmergearticles for the modified article does not actually exist in the database. | Microsoft.SQLServer.2016.Conflict_table__does_not_exist_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 21286 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Could not allocate new page for database. There are no more pages available in Filegroup. | Space can be created by dropping objects, adding additional files, or allowing file growth. | Microsoft.SQLServer.2016.Could_not_allocate_new_page_for_database_._There_are_no_more_pages_available_in_filegroup._Space_can_be_created_by_dropping_objects_adding_additional_files_or_allowing_file_growth_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 1101 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Could not allocate space for object in database because the Filegroup is full | The specified Filegroup has run out of free space. | Microsoft.SQLServer.2016.Could_not_allocate_space_for_object__in_database__because_the__filegroup_is_full_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 1105 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Could not connect to server because it is not defined as a remote login at the server | Setting up security for executing remote procedure calls (RPC) against a remote server involves setting up login mappings in the remote server and possibly in the local server running an instance of Microsoft SQL Server. The mapping is specific to a given server\instance name, usually the NetBIOS name for a default instance and the NetBIOS name plus the instance name for a named instance. If the login mapping does not exist or if the name of the server specified in the connection string does not match the exact name in the sysremotelogins table, and the guest account does not have a mapping in sysremotelogins , you will receive this error. You will also see this error if the remote user is found to have a null or empty login name. | Microsoft.SQLServer.2016.Could_not_connect_to_server_because_it_is_not_defined_as_a_remote_login_at_the_server_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 18483 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Could not create an instance of OLE DB provider | The rule triggers an alert when SQL Server could not create an instance of an OLE DB provider to connect to a linked server. | Microsoft.SQLServer.2016.Could_not_create_an_instance_of_OLE_DB_provider_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 7302 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Could not create AppDomain manager | The rule triggers an alert when SQL Server failes to create an application domain manager | Microsoft.SQLServer.2016.Could_not_create_AppDomain_manager_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 10303 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Could not create a statement object using OLE DB provider | The rule triggers an alert when SQL Server fails to create a statement object with the OLE DB provider connected to a linked server. | Microsoft.SQLServer.2016.Could_not_create_a_statement_object_using_OLE_DB_provider_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 7305 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Could not do cleanup for the killed process | This error message occurs when another error caused a user connection to terminate abnormally. | Microsoft.SQLServer.2016.Could_not_do_cleanup_for_the_killed_process_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 6103 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Could not find CHECK constraint, although the table is flagged as having one | This error can occur when the creation of a constraint failed but for some reason the creation was not completely rolled back. It can also be caused by data consistency issue with the system tables in the database where the table listed in the message resides. | Microsoft.SQLServer.2016.Could_not_find_CHECK_constraint_although_the_table_is_flagged_as_having_one_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 433 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Could not find Filegroup ID in sys.Filegroups for database | The metadata for a table contains a column ID that is greater than the largest column ID ever used in the table. This is a fatal error if the table is a system table, because the checks cannot continue when metadata is corrupt. | Microsoft.SQLServer.2016.Could_not_find_filegroup_ID_in_sys.filegroups_for_database_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8932 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Could not find FOREIGN KEY constraints for table, although the table is flagged as having them | This error can occur when the creation of a constraint failed but for some reason the creation was not completely rolled back. It can also be caused by data consistency issue with the system tables in the database where the table listed in the message resides. | Microsoft.SQLServer.2016.Could_not_find_FOREIGN_KEY_constraints_for_table_although_the_table_is_flagged_as_having_them_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 439 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Could not mark database as suspect. Getnext NC scan on sysdatabases.dbid failed | The SQL Server recovery process tried to turn on the suspect flag for the specified database, but it could not find the appropriate row in sysdatabases or could not update the database information in memory. The reason the database needs to be marked suspect should be indicated by other messages in the SQL Server error log or the Event Viewer. | Microsoft.SQLServer.2016.Could_not_mark_database_as_suspect._Getnext_NC_scan_on_sysdatabases.dbid_failed_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 3413 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Could not obtain exclusive lock on database | You may receive this error stating a lock could not be obtained for the model database if the model database is in use when you issue any CREATE DATABASE statement. Since a new database is copied from the model database, the model database has to be in a state with no activity. | Microsoft.SQLServer.2016.Could_not_obtain_exclusive_lock_on_database_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 1807 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Could not obtain information about Windows NT group/user | A process executed within SQL Server or from the SQL Server Agent, such as the xp_logininfo stored procedure, a scheduled job, or a replication agent, needs to verify the credentials of a Windows-authenticated login. The attempt to retrieve those credentials on the domain failed for an unspecified reason. | Microsoft.SQLServer.2016.Could_not_obtain_information_about_Windows_NT_group_user_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 15404 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Failed to open primary database file | An operating system error occurred when opening the primary file of a database. The error message contains the specific operating system error encountered. | Microsoft.SQLServer.2016.Could_not_open_device_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 17204 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | High | True | Application |
| MSSQL 2016: Could not open error log file | When installing Microsoft SQL Server on an NTFS partition, make sure that the NTFS file permissions allow read/write access. Otherwise, this error message may appear in the Microsoft Windows NT application log (for each installation attempt). | Microsoft.SQLServer.2016.Could_not_open_error_log_file_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 17058 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Invalid reference to File ID | This error occurs when SQL Server uses an invalid file ID while performing some operation. This error can occur for several different scenarios. | Microsoft.SQLServer.2016.Could_not_open_FCB_for_invalid_file_in_database__1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 5180 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | High | True | Application |
| MSSQL 2016: Could not open referenced table | You are trying to add, drop, or modify a constraint on a table that has a schema stability lock (LCK_M_SCH_S or Sch-S) held on it. The schema stability lock is not compatible with DDL. The lock may be held by a query involving this table that is taking a long time to compile. | Microsoft.SQLServer.2016.Could_not_open_referenced_table_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 436 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Could not open tempdb. Cannot continue | The tempdb database could not be opened. The possible reasons for this could include: | Microsoft.SQLServer.2016.Could_not_open_tempdb.__Cannot_continue_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 1619 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Could not read and latch page | The page read failed for some reason (see any accompanying errors), or a latch could not be taken (there may be latch timeout messages on the error log). | Microsoft.SQLServer.2016.Could_not_read_and_latch_page_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8966 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Could not recover database due to unresolved transaction outcomes | The recovery process found pending transactions for the specified database. These transactions were either distributed transactions that used Microsoft Distributed Transaction Coordinator (MS DTC), or the transactions were single instance cross-database transactions. There is not enough information available for the recovery process to either commit or roll back one or more of those transactions. | Microsoft.SQLServer.2016.Could_not_recover_database_due_to_unresolved_transaction_outcomes_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 3431 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Could not resolve the referenced column name in table | This error occurs when you try to modify data in a table with a foreign key that references a column that no longer exists in the referenced table. Merely renaming a column will not cause this error. Under normal circumstances, a column referenced by a foreign key cannot be dropped, so this error may indicate that unsupported direct system table updates have occurred. | Microsoft.SQLServer.2016.Could_not_resolve_the_referenced_column_name_in_table_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 437 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Could not write a CHECKPOINT record in database because the log is out of space | The transaction log for the specified database has reached its capacity. The limit could be due to a configuration setting or to the amount of physical space available for one or more of the files configured for this database. | Microsoft.SQLServer.2016.Could_not_write_a_CHECKPOINT_record_in_database_because_the_log_is_out_of_space_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 3619 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: CREATE DATABASE failed. Could not allocate enough disk space for a new database on the named disks | This error occurs when there is not enough space on the device to create the model database. | Microsoft.SQLServer.2016.CREATE_DATABASE_failed._Could_not_allocate_enough_disk_space_for_a_new_database_on_the_named_disks_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 1803 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: DB Active Connections Count | SQL 2016 DBs Active Connections performance collection rule | Microsoft.SQLServer.2016.Database.ActiveConnections.Collection | Microsoft.SQLServer.2016.Database | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB Active Requests Count | SQL 2016 DBs Active Requests performance collection rule | Microsoft.SQLServer.2016.Database.ActiveRequests.Collection | Microsoft.SQLServer.2016.Database | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB Active Sessions Count | SQL 2016 DBs Active Sessions performance collection rule | Microsoft.SQLServer.2016.Database.ActiveSessions.Collection | Microsoft.SQLServer.2016.Database | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB Active Transactions Count | SQL 2016 DBs Active Transactions performance collection rule | Microsoft.SQLServer.2016.Database.ActiveTransactionsDB.Collection | Microsoft.SQLServer.2016.Database | PerformanceCollection | True | $Target/Host/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Databases | Active Transactions | 900 | 0 | | False | | | True | |
| MSSQL 2016: DB Allocated Free Space (MB) | SQL 2016 DB Allocated Free Space (MB) performance collection rule | Microsoft.SQLServer.2016.Database.DBAllocatedFreeSpaceMB.Collection | Microsoft.SQLServer.2016.Database | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB Free Outer Space (MB) | SQL 2016 DBs Free Outer Space (MB) performance collection rule | Microsoft.SQLServer.2016.Database.DBDiskFreeSpaceMB.Collection | Microsoft.SQLServer.2016.Database | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB Allocated Space (MB) | Collect database allocated size | Microsoft.SQLServer.2016.Database.DBSize.Collection | Microsoft.SQLServer.2016.Database | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB Free Space Total (MB) | The amount of space left in database for all files in all Filegroups for this database in megabytes. Also includes space left on media hosting a file with autogrowth enabled.
Please note that this rule collects metrics for ROWS data only. Metrics for FILESTREAM and for In-Memory OLTP data are ignored. | Microsoft.SQLServer.2016.Database.DBSpaceFree.Collection | Microsoft.SQLServer.2016.Database | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB Free Space Total (\%) | The amount of space left in database for all files in all Filegroups for this database in percentage terms. Also includes space left on media hosting a file with autogrowth enabled.
Please note that this rule collects metrics for ROWS data only. Metrics for FILESTREAM and for In-Memory OLTP data are ignored. | Microsoft.SQLServer.2016.Database.DBSpaceFreePercent.Collection | Microsoft.SQLServer.2016.Database | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB Allocated Space Used (MB) | SQL 2016 DBs Allocated Space Used (MB) performance collection rule | Microsoft.SQLServer.2016.Database.DBUsedSpaceMB.Collection | Microsoft.SQLServer.2016.Database | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB Disk Read Latency (ms) | SQL 2016 DB Disk Read Latency (ms) performance collection rule. Gets maximum read disk latency from all logical disk which host database files | Microsoft.SQLServer.2016.Database.DiskReadLatency.Collection | Microsoft.SQLServer.2016.Database | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB Disk Write Latency (ms) | SQL 2016 DB Disk Write Latency (ms) performance collection rule. Gets maximum Write disk latency from all logical disk which host database files. | Microsoft.SQLServer.2016.Database.DiskWriteLatency.Collection | Microsoft.SQLServer.2016.Database | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB Transaction Log Free Space Total (\%) | Collect unused transaction log space reported by SQL Server as a percentage of total transaction log space | Microsoft.SQLServer.2016.Database.TransactionLogSpaceFreePercent.Collection | Microsoft.SQLServer.2016.Database | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB Transactions Per Second Count | SQL 2016 DBs Transactions per second performance collection rule | Microsoft.SQLServer.2016.Database.TransactionsPerSecDB.Collection | Microsoft.SQLServer.2016.Database | PerformanceCollection | True | $Target/Host/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Databases | Transactions/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Database Backup Failed To Complete | BACKUP failed to complete the command. | Microsoft.SQLServer.2016.Database_Backup_Failed_To_Complete_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 3041 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Database cannot be opened due to inaccessible files or insufficient memory or disk space | Error 945 is returned when the database is marked IsShutdown . This occurs when a database cannot be recovered due to missing files, or some other resource error that usually can be corrected easily. | Microsoft.SQLServer.2016.Database_cannot_be_opened_due_to_inaccessible_files_or_insufficient_memory_or_disk_space._See_the_SQL_Server_errorlog_for_details_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 945 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Failure occurred during database recovery | This error occurs when SQL Server fails to recover a database successfully when it is brought online. | Microsoft.SQLServer.2016.Database_could_not_recover_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 3414 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | High | True | Application |
| MSSQL 2016: Database log file is full. Back up the transaction log for the database to free up some log space | The specified transaction log file has run out of free space. | Microsoft.SQLServer.2016.Database_log_file_is_full._Back_up_the_transaction_log_for_the_database_to_free_up_some_log_space_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 9002 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Database consistency errors found | This message indicates a database consistency check has encountered errors and none or not all of the errors were repaired. | Microsoft.SQLServer.2016.DBCC_executed_found_and_not_repaired_errors_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 0 | | True | Error | High | True | Application |
| MSSQL 2016: Database consistency errors found and repaired | This message indicates a database consistency check has encountered errors and all of the errors were repaired. | Microsoft.SQLServer.2016.DBCC_executed_found_and_repaired_errors_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 0 | | True | Error | High | True | Application |
| MSSQL 2016: Database consistency check performed with no errors | This message indicates a database consistency check has been run but no errors were encountered. | Microsoft.SQLServer.2016.DBCC_executed_found_no_errors_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 0 | | True | Information | Low | True | Application |
| MSSQL 2016: DB Engine Average Wait Time (ms) | SQL 2016 DB Engine Average Wait Time performance collection rule | Microsoft.SQLServer.2016.DBEngine.AverageWaitTime.Collection | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Locks | Average Wait Time (ms) | 900 | 0 | | False | | | True | |
| MSSQL 2016: DB Engine CPU Utilization (\%) | SQL 2016 DB Engine CPU Utilization (\%) performance collection rule. | Microsoft.SQLServer.2016.DBEngine.CPUUsagePercent.Collection | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB Engine Page Life Expectancy (s) | SQL 2016 DB Engine Page Life Expectancy (s) performance collection rule | Microsoft.SQLServer.2016.DBEngine.PageLifeExpectancy.Collection | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB Engine Stolen Server Memory (MB) | SQL 2016 DB Engine Stolen Server Memory (MB) performance collection rule | Microsoft.SQLServer.2016.DBEngine.StolenServerMemory.Collection | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB Engine Thread Count | SQL 2016 DB Engine Thread Count performance collection rule | Microsoft.SQLServer.2016.DBEngine.ThreadCount.Collection | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: SQL Server 2016 DB Engine is restarted | Detects SQL Server 2016 DB Engine restart. Note: This rule is disabled by default. Please use overrides to enable it when necessary. | Microsoft.SQLServer.2016.DBEngineServiceRestart | Microsoft.SQLServer.2016.DBEngine | AvailabilityHealth | False | | | 0 | 0 | | True | Warning | Normal | True | |
| MSSQL 2016: DB File Allocated Free Space (MB) | The amount of space left in a file in megabytes. Does not include space left on media hosting a file with autogrowth enabled. | Microsoft.SQLServer.2016.DBFile.FileAllocatedSpaceLeftMB.Collection | Microsoft.SQLServer.2016.DBFile | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB File Allocated Free Space (\%) | The amount of space left in a file in percentage terms. Does not include space left on media hosting a file with autogrowth enabled | Microsoft.SQLServer.2016.DBFile.FileAllocatedSpaceLeftPercent.Collection | Microsoft.SQLServer.2016.DBFile | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB File Free Space Total (MB) | The amount of space left in a file in megabytes. Also includes space left on media hosting a file with autogrowth enabled. | Microsoft.SQLServer.2016.DBFile.SpaceFreeMegabytes.Collection | Microsoft.SQLServer.2016.DBFile | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB File Free Space Total (\%) | The amount of space left in a file in percentage terms. Also includes space left on media hosting a file with autogrowth enabled. | Microsoft.SQLServer.2016.DBFile.SpaceFreePercent.Collection | Microsoft.SQLServer.2016.DBFile | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB Filegroup Allocated Free Space (MB) | The amount of space left in all files for this Filegroup in megabytes. Does not include space left on media hosting a file with autogrowth enabled. | Microsoft.SQLServer.2016.DBFileGroup.FileGroupAllocatedSpaceLeftMB.Collection | Microsoft.SQLServer.2016.DBFileGroup | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB Filegroup Allocated Free Space (\%) | The amount of space left in all files for this Filegroup in percentage terms. Does not include space left on media hosting a file with autogrowth enabled. | Microsoft.SQLServer.2016.DBFileGroup.FileGroupAllocatedSpaceLeftPercent.Collection | Microsoft.SQLServer.2016.DBFileGroup | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB Filegroup Free Space Total (MB) | The amount of space left in all files for this Filegroup in megabytes. Also includes space left on media hosting a file with autogrowth enabled. | Microsoft.SQLServer.2016.DBFileGroup.SpaceFreeMegabytes.Collection | Microsoft.SQLServer.2016.DBFileGroup | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB Filegroup Free Space Total (\%) | Collects free database Filegroup space in percentage terms. | Microsoft.SQLServer.2016.DBFileGroup.SpaceFreePercent.Collection | Microsoft.SQLServer.2016.DBFileGroup | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB FILESTREAM Filegroup Free Space Total (MB) | Collects free FILESTREAM Filegroup data container space in megabytes. | Microsoft.SQLServer.2016.DBFileStream.FileGroup.SpaceFreeMegabytes.Collection | Microsoft.SQLServer.2016.DBFileGroupFd | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB FILESTREAM Filegroup Free Space Total (\%) | Collects free FILESTREAM Filegroup data container space in percentage terms. | Microsoft.SQLServer.2016.DBFileStream.FileGroup.SpaceFreePercent.Collection | Microsoft.SQLServer.2016.DBFileGroupFd | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB Log File Allocated Free Space (MB) | The amount of space left in all log files for this database in megabytes. Does not include space left on media hosting a file with autogrowth enabled. | Microsoft.SQLServer.2016.DBLogFile.FileAllocatedSpaceLeftMB.Collection | Microsoft.SQLServer.2016.DBLogFile | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB Log File Allocated Free Space (\%) | The amount of space left in all log files for this database in percentage terms. Does not include space left on media hosting a file with autogrowth enabled. | Microsoft.SQLServer.2016.DBLogFile.FileAllocatedSpaceLeftPercent.Collection | Microsoft.SQLServer.2016.DBLogFile | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB Log File Free Space Total (MB) | The amount of space left in all log files for this database in megabytes. Also includes space left on media hosting a file with autogrowth enabled. | Microsoft.SQLServer.2016.DBLogFile.SpaceFreeMegabytes.Collection | Microsoft.SQLServer.2016.DBLogFile | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: DB Log File Free Space Total (\%) | The amount of space left in all log files for this database in percentage terms. Also includes space left on media hosting a file with autogrowth enabled. | Microsoft.SQLServer.2016.DBLogFile.SpaceFreePercent.Collection | Microsoft.SQLServer.2016.DBLogFile | PerformanceCollection | True | | | 0 | 0 | | False | | | True | |
| MSSQL 2016: Descriptor for object in database not found in the hash table during attempt to unhash it | A temporary table could not be found. The specific object ID will be available in the Windows Application log as event ID 617. | Microsoft.SQLServer.2016.Descriptor_for_object_in_database_not_found_in_the_hash_table_during_attempt_to_unhash_it_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 617 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Distributed transaction was aborted by MSDTC | The rule triggers an alert when Distributed transaction was aborted by MSDTC. | Microsoft.SQLServer.2016.Distributed_transaction_aborted_by_MSDTC_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8522 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Enlist of MSDTC transaction failed | The rule triggers an alert when SQL Server fails to enlist a new or existing distributed transaction. | Microsoft.SQLServer.2016.Enlist_of_MSDTC_transaction_failed_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8510 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Error recovering database. Could not connect to MSDTC to check the completion status of transaction | When you are using MS DTC to manage a distributed transaction across multiple servers and a loss of connectivity occurs, the distributed transaction is left in an unknown or "in doubt" state. Common sources of interruptions are | Microsoft.SQLServer.2016.Error_recovering_database_._Could_not_connect_to_MSDTC_to_check_the_completion_status_of_transaction_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 3437 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Error while undoing logged operation in database | The recovery process could not undo (roll back) one or more transactions in the specified database. This error will be accompanied by a more specific error in the SQL Server error log and/or the event log. | Microsoft.SQLServer.2016.Error_while_undoing_logged_operation_in_database__1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 3314 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Cannot create file | SQL Server cannot create file because the file already exists. | Microsoft.SQLServer.2016.EventCollectionRule.DBEngine.CannotCreateFile | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 5170 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: CREATE FILE encountered operating system error | CREATE FILE encountered operating system error. | Microsoft.SQLServer.2016.EventCollectionRule.DBEngine.CreateFileEncounteredOperatingSystemError | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 5123 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: SQL Server Out Of Memory | SQL Server has failed to allocate the sufficient amount of memory to run the query. | Microsoft.SQLServer.2016.EventCollectionRule.DBEngine.SQLServerOutOfMemory | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 701 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Unable to open the physical file | SQL Server has failed to open the physical file.. | Microsoft.SQLServer.2016.EventCollectionRule.DBEngine.UnableToOpenThePhysicalFile | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 5120 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Failed to add column to table | sp_repladdcolumn failed to add the specified column to the table in the publication database. If another error is reported along with this one, the other error should indicate the reason the column could not be added. If no other error is reported, the problem could be that the owner-qualified table does not exist, or the data type is not one that can be added to a replicated table. The data type of the new column must either be an identity, computed, or timestamp column; allow nulls; or have a default. For more information about sp_repladdcolumn, see "Schema Changes on Publication Databases" in Books Online. | Microsoft.SQLServer.2016.Failed_to_add_column__to_table__1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 21285 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Failed to allocate memory for Common Language Runtime (CLR) | The rule triggers an alert when SQL Server is unable to allocate memory for CLR. | Microsoft.SQLServer.2016.Failed_to_allocate_memory_for_Common_Language_Runtime__CLR__5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 6289 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Failed to create AppDomain | The rule triggers an alert when an application tried to create an application domain, but failed. This may be caused when there is not enough memory to start the application domain. | Microsoft.SQLServer.2016.Failed_to_create_AppDomain_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 6517 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Failed to drop column from table | sp_repldropcolumn failed to drop the specified column on the publication database. The error could result from a failed system table update or from a failure of the underlying ALTER TABLE statement. | Microsoft.SQLServer.2016.Failed_to_drop_column__from_table__1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 21284 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Failed to finish full-text operation. The Filegroup is empty, read-only, or not online | The full-text operation did not finish because the Filegroup is empty, read-only, or not online. | Microsoft.SQLServer.2016.Failed_to_finish_full_text_operation._The_filegroup_is_empty_read_only_or_not_online_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 9964 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Failed to initialize the Common Language Runtime (CLR) due to memory pressure | Windows could not allocate memory for the Microsoft Common Language Runtime (CLR) to initialize. | Microsoft.SQLServer.2016.Failed_to_initialize_the_Common_Language_Runtime__CLR__due_to_memory_pressure_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 6513 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Failed to initialize the Common Language Runtime (CLR) with HRESULT | The rule triggers an alert when an assembly or application fails to start and logs an HRESULT error. | Microsoft.SQLServer.2016.Failed_to_initialize_the_Common_Language_Runtime__CLR__with_HRESULT_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 6511 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Failed to initialize the Common Language Runtime (CLR) with HRESULT | The rule triggers an alert when an assembly or an application fails to start and logs an HRESULT error. The Windows application log may contain an information about specific HRESULT. | Microsoft.SQLServer.2016.Failed_to_initialize_the_Common_Language_Runtime__CLR__with_HRESULT_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 6512 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Failed to restore master database. Shutting down SQL Server | The backup of the master database that you are restoring is not usable. The file itself may have been corrupted, or the original master database from which the backup was taken may have data integrity problems. | Microsoft.SQLServer.2016.Failed_to_restore_master_database._Shutting_down_SQL_Server_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 3151 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Full Text Search: An unknown full-text failure occurred | This error can occur in various circumstances. Often it is related to permissions or missing files. | Microsoft.SQLServer.2016.Full_Text_Search___An_unknown_full_text_failure_occurred_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 7608 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Full Text Search: Could not find full-text index for database | The specified full-text index is unavailable. | Microsoft.SQLServer.2016.Full_Text_Search___Could_not_find_full_text_index_for_database_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 7606 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Full Text Search: Full-text catalog is in an unusable state. Drop and re-create this full-text catalog | The full-text catalog is offline. The full-text directory has been deleted, is corrupt, or the path points to a location that is not valid. | Microsoft.SQLServer.2016.Full_Text_Search___Full_text_catalog_is_in_a_unusable_state._Drop_and_re_create_this_full_text_catalog_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 7624 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Full Text Search: Full-text catalog lacks sufficient disk space to complete this operation | There is not enough disk space to hold the full-text catalog. | Microsoft.SQLServer.2016.Full_Text_Search___Full_text_catalog_lacks_sufficient_disk_space_to_complete_this_operation_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 7622 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Full Text Search: Full-Text Search is not enabled for the current database. Use sp_fulltext_database to enable Full-Text Search | You have attempted to perform a full-text indexing in a database that is not enabled for full-text indexing. The database may have never been enabled for full-text, or it may have been restored or attached, which will automatically disable full-text indexing. | Microsoft.SQLServer.2016.Full_Text_Search___Full_Text_Search_is_not_enabled_for_the_current_database._Use_sp_fulltext_database_to_enable_Full_Text_Search_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 15601 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Full Text Search: Search on full-text catalog failed with unknown result | The full-text query failed for an unspecified reason. | Microsoft.SQLServer.2016.Full_Text_Search___Search_on_full_text_catalog_failed_with_unknown_result_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 7607 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Indexed view does not contain all rows that the view definition produces. | Refer to Books Online for more information on this error. This does not necessarily represent an integrity issue with the data in this database. | Microsoft.SQLServer.2016.Indexed_view_does_not_contain_all_rows_that_the_view_definition_produces.__Refer_to_Books_Online_for_more_information_on_this_error.__This_does_not_necessarily_represent_an_integrity_issue_with_th_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8908 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Internal Query Processor Error: The query processor could not obtain access to a required interface | This is an internal query processor error. | Microsoft.SQLServer.2016.Internal_Query_Processor_Error__The_query_processor_could_not_obtain_access_to_a_required_interface_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8601 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Internal Query Processor Error: The query processor encountered an internal limit overflow | This is an internal query processor error. | Microsoft.SQLServer.2016.Internal_Query_Processor_Error__The_query_processor_encountered_an_internal_limit_overflow_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8620 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Internal Query Processor Error: The query processor encountered an unexpected error during execution | This is an internal query processor error. | Microsoft.SQLServer.2016.Internal_Query_Processor_Error__The_query_processor_encountered_an_unexpected_error_during_execution_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8630 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Internal Query Processor Error: The query processor encountered an unexpected error during the processing of a remote query phase | This is an internal query processor error. | Microsoft.SQLServer.2016.Internal_Query_Processor_Error__The_query_processor_encountered_an_unexpected_error_during_the_processing_of_a_remote_query_phase_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8680 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Internal Query Processor Error: The query processor ran out of stack space during query optimization | The Query Processor is using a large but limited memory stack when optimizing queries. In some extreme situations the stack size may become a limit for a given very large query--for example, a query containing an inlist with 100,000 constants. | Microsoft.SQLServer.2016.Internal_Query_Processor_Error__The_query_processor_ran_out_of_stack_space_during_query_optimization_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8621 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Invalid reference to LOB page | This error occurs when SQL Server uses an invalid reference to a LOB page in an operation. This error may occur due to several different reasons. | Microsoft.SQLServer.2016.Invalid_reference_to_LOB_page_id7105 | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 7105 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | High | True | Application |
| MSSQL 2016: I/O Request Takes Longer To Complete | This rule generates an alert when In/Out request takes longer than 15 seconds to complete. The rule is disabled by default. | Microsoft.SQLServer.2016.IORequestsTakingLongerThen15SecondsToComplete | Microsoft.SQLServer.2016.DBEngine | EventCollection | False | | | 0 | 833 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: IO Completion Listener Worker appears to be non-yielding on Node | I/O completion ports are the mechanism by which Microsoft SQL Server uses a pool of threads that was created when the service was started to process asynchronous I/O requests. The message will specify what node the completion port is not yielding on. Note: This rule is disabled by default. Please use overrides to enable it when necessary. | Microsoft.SQLServer.2016.IO_Completion_Listener_Worker_appears_to_be_non_yielding_on_Node_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | False | | | 0 | 17887 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Job step cannot be run because the subsystem failed to load | A SQL Server job failed to run because the SQL Server Agent subsystem failed to load. | Microsoft.SQLServer.2016.Job_step_cannot_be_run_because_the_subsystem_failed_to_load_1_5_Rule | Microsoft.SQLServer.2016.Agent | EventCollection | True | | | 0 | 212 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.Agent"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Number of Lockrequests Per Second | Collects the Windows "Number of Lockrequests Per Second" performance counter for each instance of SQL 2016 DB Engine. | Microsoft.SQLServer.2016.LockRequestsPerSecond | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Locks | Lock Requests/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Lock Timeouts Per Second | Collects the Windows "Lock Timeouts Per Second" performance counter for each instance of SQL 2016 DB Engine. | Microsoft.SQLServer.2016.LockTimeoutsPerSecond | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Locks | Lock Timeouts/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Number of Lockwaits Per Second | Collects the Windows "Number of Lockwaits Per Second" performance counter for each instance of SQL 2016 DB Engine. | Microsoft.SQLServer.2016.LockWaitsPerSecond | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Locks | Lock Waits/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Logical consistency error after performing I/O on page | A consistency check failed when reading or writing a database page or transaction log block. The error message contains the specific type of consistency check that failed. | Microsoft.SQLServer.2016.Logical_consistency_error_after_performing_IO_on_page_id824 | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 824 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | High | True | Application |
| MSSQL 2016: Logical page in database is already hashed | This error occurs when SQL Server attempts to hash the logical page \%S_PGID of database ID\%d and the page is already in the SQL Server hash table. | Microsoft.SQLServer.2016.Logical_page_in_database_is_already_hashed_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 813 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Logins per Second | Total number of logins started per second. This does not include pooled connections. | Microsoft.SQLServer.2016.LoginsPerSecCollection | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:General Statistics | Logins/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Login failed. The workstation licensing limit for SQL Server access has already been reached | SQL Server will not provide connections to workstations after the licensing limit has been reached. | Microsoft.SQLServer.2016.Login_failed._The_workstation_licensing_limit_for_SQL_Server_access_has_already_been_reached_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 18459 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Login failed | When a connection attempt is rejected because of an authentication failure that involves a bad password or user name, a message similar to the following is returned to the client: "Login failed for user 'user_name'. (Microsoft SQL Server, Error: 18456)".
Note: this rule might be noisy in some environments. Therefore, it is disabled by default. Please use overrides to enable it when necessary. | Microsoft.SQLServer.2016.Login_failed__Account | Microsoft.SQLServer.2016.DBEngine | EventCollection | False | | | 0 | 18456 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Login failed: Account locked out | A user attempted to log into the network with an account that has been locked out. The Windows security log will identify the user name under MSSQLSERVER event ID 18486. | Microsoft.SQLServer.2016.Login_failed__Account_locked_out_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 18486 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Login failed: Error during validation | A user attempted to log in to SQL Server. An unexpected error occurred during validation. The Windows security log will identify the user name and error ID under MSSQLSERVER event ID 18468. | Microsoft.SQLServer.2016.Login_failed__Error_during_validation_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 18468 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Login failed: Password cannot be used at this time | A user attempted to change the password, but the proposed password could not be used at this time. The Windows security log will identify the user name under MSSQLSERVER event ID 18463. | Microsoft.SQLServer.2016.Login_failed__Password_cannot_be_used_at_this_time_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 18463 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Login failed: Password expired | A user attempted to log into SQL Server with an expired password. The Windows security log will identify the user name under event ID 18487. | Microsoft.SQLServer.2016.Login_failed__Password_expired_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 18487 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Login failed: Password fails password filter DLL requirements | A user tried to access SQL Server with a password that did not meet the requirements of the password filter DLL. Windows security log will identify the user name under MSSQLSERVER event ID 18467. | Microsoft.SQLServer.2016.Login_failed__Password_fails_password_filter_DLL_requirements_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 18467 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Login failed: Password must be changed | A user attempted to log into SQL Server with a password that was set to the MUST_CHANGE option. The user will be identified in the Windows security log under MSSQLSERVER event ID 18488. | Microsoft.SQLServer.2016.Login_failed__Password_must_be_changed_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 18488 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Login failed: Password too long | A user attempted to create a password, but the proposed password was too long. The Windows security log will identify the user name under MSSQLSERVER event ID 18465. | Microsoft.SQLServer.2016.Login_failed__Password_too_long_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 18465 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Login failed: Password too short | A user attempted to change the password, but the proposed password was too short. The Windows security log will identify the user name under MSSQLSERVER event ID 18464. | Microsoft.SQLServer.2016.Login_failed__Password_too_short_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 18464 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Login failed: Password too simple | A user attempted to create a password, but the proposed password did not meet the Windows password complexity requirements policy. These are defined in the Password must meet complexity requirements policy setting. The Windows security log will identify the user name under MSSQLSERVER event ID 18466. | Microsoft.SQLServer.2016.Login_failed__Password_too_simple_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 18466 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Log Backup Failed to Complete | This error indicates that SQL Server could not complete the BACKUP of the specified database due to a previous error. The BACKUP command that failed is given at the end of the error message. This message also appears in the Windows Application log. | Microsoft.SQLServer.2016.Log_Backup_Failed_to_Complete_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 3041 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Maximum limit for connections has been reached | By default, SQL Server dynamically manages the memory needed for user connections. However, the maximum number of connections can be set to a fixed value by setting the user connections configuration option to a value other than 0. Setting the user connections option to a non-zero value is not recommended. If this option is set to a non-zero value and the specified number of connections is exceeded, any additional login attempts will fail with the above message. If the value is set to 1, the SQL Server instance may not start. | Microsoft.SQLServer.2016.Maximum_limit_for_connections_has_been_reached_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 17809 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Monitoring failed | The rule traces failed monitoring workflows and generates error alerts. | Microsoft.SQLServer.2016.MonitoringFailed.Rule | Microsoft.SQLServer.2016.EventLogCollectionTarget | Alert | True | | | 0 | 0 | | True | Error | Normal | True | Operations Manager |
| MSSQL 2016: Monitoring warning | The rule traces problematic monitoring workflows and generates warning alerts. | Microsoft.SQLServer.2016.MonitoringWarning.Rule | Microsoft.SQLServer.2016.EventLogCollectionTarget | Alert | True | | | 0 | 0 | | True | Warning | Normal | True | Operations Manager |
| MSSQL 2016: MSDTC on server is unavailable | The rule triggers an alert when MSDTC on the server is unavailable. | Microsoft.SQLServer.2016.MSDTC_on_server__is_unavailable_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8501 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: No slots are free to keep buffers for table | This is raised when SQL Server 2016 has an internal error. | Microsoft.SQLServer.2016.No_slots_are_free_to_keep_buffers_for_table__1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 654 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Number of Deadlocks Per Second | Collects the Windows "Number of Deadlocks Per Second" performance counter for each instance of SQL 2016 DB Engine. | Microsoft.SQLServer.2016.NumberDeadlocksPerSecond | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Locks | Number of Deadlocks/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: One or more indexes are damaged and must be repaired or dropped | This error provides more details about the problem described in error 8952. See that error for an explanation. | Microsoft.SQLServer.2016.One_or_more_indexes_are_damaged_and_must_be_repaired_or_dropped_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8956 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Failed to open database or transaction log file | An operating system error occurred when opening a transaction log file or a secondary database file of a database. The error message contains the specific operating system error encountered. | Microsoft.SQLServer.2016.Operating_system_error_during_creation_opening_of_physical_device_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 17207 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | High | True | Application |
| MSSQL 2016: Operating System error encountered | This message indicates that an error of some sort was returned from the operating system to a process within SQL Server. The process listed at the beginning of the message indicates which function within SQL Server received the error from the operating system. The exact operating system error number and text at the end of the message will vary depending on what problem the operating system encountered. This error is almost always seen in conjunction with other errors. | Microsoft.SQLServer.2016.Operating_System_error_encountered_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 17053 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Operating system error on a device | The backup device cannot be opened. | Microsoft.SQLServer.2016.Operating_system_error_on_a_device_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 17218 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Optimized concurrent query limit has been exceeded | You are using an edition of SQL Server that is licensed for a limited number of concurrent queries. This includes the Personal and Desktop editions. Those editions have a concurrent workload governor that limits them to a specific number of concurrent user queries plus a smaller number of concurrent system tasks. | Microsoft.SQLServer.2016.Optimized_concurrent_query_limit_has_been_exceeded_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 3629 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: OS Error occurred while performing I/O on page | An operating system error occurred when reading or writing a database page. The error message contains the specific operating system error encountered. | Microsoft.SQLServer.2016.OSError_Occurred_While_Performing_IO_onpage_id823 | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 823 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | High | True | Application |
| MSSQL 2016: Permission denied on object | This error occurs when a Microsoft SQL Server user attempts an action, such as executing a stored procedure, or reading or modifying a table, for which the user does not have the appropriate privileges. | Microsoft.SQLServer.2016.Permission_denied_on_object_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 229 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Physical File Access Error | This rule generates an alert when a file activation error occurs. The rule is disabled by default. | Microsoft.SQLServer.2016.PhysicalFileAccessErrorRule | Microsoft.SQLServer.2016.DBEngine | EventCollection | False | | | 0 | 5105 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Potential deadlocks exist on all schedulers on Node | This message is raised when the server fails to respond to new queries within a certain time limit. | Microsoft.SQLServer.2016.Potential_deadlocks_exist_on_all_schedulers_on_Node_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 17884 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Process Worker appears to be non-yielding on Scheduler | This error indicates that there is a possible problem with a thread not yielding on a scheduler. Note: This rule is disabled by default. Please use overrides to enable it when necessary. | Microsoft.SQLServer.2016.Process_Worker_appears_to_be_non_yielding_on_Scheduler_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | False | | | 0 | 17883 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Recovery of database detected possible identity value inconsistency in table | The database recovery process could not determine the current identity value for the specified table. | Microsoft.SQLServer.2016.Recovery_of_database__detected_possible_identity_value_inconsistency_in_table_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 3452 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: RESTORE could not start database | Internal structures could not be created during the database RESTORE. This is usually the side effect of another error. | Microsoft.SQLServer.2016.RESTORE_could_not_start_database_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 3167 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: XTP Background Thread Error | The rule listens to event 41354 and raises a warning alert if the event is added to the log. | Microsoft.SQLServer.2016.Rule.XTP.BackgroundThreadError | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 41354 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: XTP Background Thread Error Log | The rule listens to event 41355 and raises a warning alert if the event is added to the log. | Microsoft.SQLServer.2016.Rule.XTP.BackgroundThreadErrorLog | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 41355 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: XTP Compiler Failure | The rule listens to event 41313 and raises a warning alert if the event is added to the log. | Microsoft.SQLServer.2016.Rule.XTP.CompilerFailure | Microsoft.SQLServer.2016.DBEngine | EventCollection | False | | | 0 | 41313 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: XTP Insufficient Disk Space | The rule listens to event 41822 and raises a critical alert if the event is added to the log. | Microsoft.SQLServer.2016.Rule.XTP.InsufficientDiskSpace | Microsoft.SQLServer.2016.DBEngine | EventCollection | False | | | 0 | 41822 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: XTP Unable Call Compiler | The rule listens to event 41312 and raises a warning alert if the event is added to the log. | Microsoft.SQLServer.2016.Rule.XTP.UnableCallCompiler | Microsoft.SQLServer.2016.DBEngine | EventCollection | False | | | 0 | 41312 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: XTP Unable Load Compiled Dll | The rule listens to event 41309 and raises a warning alert if the event is added to the log. | Microsoft.SQLServer.2016.Rule.XTP.UnableLoadCompiledDll | Microsoft.SQLServer.2016.DBEngine | EventCollection | False | | | 0 | 41309 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| [Deprecated] MSSQL 2016: Workflow failed to connect to the target system | A monitoring or discovery script doesn’t have permissions to connect to the database or database is not accessible. This rule is considered to be obsolete in this Management Pack. | Microsoft.SQLServer.2016.Script_Failed_Database_Login | Microsoft.SQLServer.2016.DBEngine | Alert | False | | | 0 | 4211 | Health Service Script | True | Error | Normal | True | Operations Manager |
| MSSQL 2016: Service Broker was not able to allocate memory for cryptographic operations | The rule triggers an alert when SQL Server Service Broker is not able to allocate memory for cryptographic operations. | Microsoft.SQLServer.2016.Service_Broker_was_not_able_to_allocate_memory_for_cryptographic_operations_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 9634 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: SQL Compilations Per Second | Collects the Windows "SQL Compilations Per Second" performance counter for each instance of SQL 2016 DB Engine. | Microsoft.SQLServer.2016.SQLCompilationsPerSecond | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:SQL Statistics | SQL Compilations/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: SQL Re-Compilations Per Second | Collects the Windows "SQL Recompiles Per Second" performance counter for each instance of SQL 2016 DB Engine. | Microsoft.SQLServer.2016.SQLRecompilesPerSecond | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:SQL Statistics | SQL Re-Compilations/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: SQL Server Agent could not be started | A process or a person attempted to start the SQL Server Agent service, but the service did not start. | Microsoft.SQLServer.2016.SQLServerAgent_could_not_be_started_1_5_Rule | Microsoft.SQLServer.2016.Agent | EventCollection | True | | | 0 | 103 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.Agent"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: SQL Server Agent initiating self-termination | SQL Server Agent has shut down the SQL Server Agent service. | Microsoft.SQLServer.2016.SQLServerAgent_initiating_self_termination_1_5_Rule | Microsoft.SQLServer.2016.Agent | EventCollection | True | | | 0 | 51 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.Agent"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Broker Activation: Stored Procedures Invoked Per Second | This counter reports the total number of activation stored procedures invoked by all queue monitors in the instance per second. This counter is polled every fifteen minutes. | Microsoft.SQLServer.2016.SQLServer_Broker_Activation_Stored_Procedures_Invoked_sec__Total_15.0_minutes_5_Rule | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Broker Activation | Stored Procedures Invoked/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Broker Activation: Tasks Aborted Per Second | This counter reports the total number of activation stored procedure tasks that end with an error, or are aborted by a queue monitor for failing to receive messages. This counter is polled every fifteen minutes. | Microsoft.SQLServer.2016.SQLServer_Broker_Activation_Tasks_Aborted_sec__Total_15.0_minutes_5_Rule | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Broker Activation | Tasks Aborted/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Broker Activation: Tasks Started Per Second | This counter reports the total number of activation stored procedures started per second by all queue monitors in the instance. This counter is polled every fifteen minutes. | Microsoft.SQLServer.2016.SQLServer_Broker_Activation_Tasks_Started_sec__Total_15.0_minutes_5_Rule | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Broker Activation | Tasks Started/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Broker Activation: Task Limit Reached Per Second | This counter reports the number of times per second that a queue monitor would have started a new task, but did not because the maximum number of tasks for the queue is already running. This counter is polled every fifteen minutes. | Microsoft.SQLServer.2016.SQLServer_Broker_Activation_Task_Limit_Reached_sec__Total_15.0_minutes_5_Rule | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Broker Activation | Task Limit Reached/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Broker Activation: Task Limit Reached | This counter reports the total number of times that a queue monitor would have started a new task, but did not because the maximum number of tasks for the queue is already running. This counter is polled every fifteen minutes. | Microsoft.SQLServer.2016.SQLServer_Broker_Activation_Task_Limit_Reached__Total_15.0_minutes_5_Rule | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Broker Activation | Task Limit Reached | 900 | 0 | | False | | | True | |
| MSSQL 2016: Broker Statistics: Broker Transaction Rollbacks | The number of rolled back transactions that contained DML-related to Service Broker. This counter is polled every fifteen minutes. | Microsoft.SQLServer.2016.SQLServer_Broker_Statistics_Broker_Transaction_Rollbacks_15.0_minutes_5_Rule | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Broker Statistics | Broker Transaction Rollbacks | 900 | 0 | | False | | | True | |
| MSSQL 2016: Broker Statistics: Enqueued Messages Per Second | The number of messages per second that have been placed onto the queues in the instance. This counter is polled every fifteen minutes. | Microsoft.SQLServer.2016.SQLServer_Broker_Statistics_Enqueued_Messages_sec_15.0_minutes_5_Rule | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Broker Statistics | Enqueued Messages/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Broker Statistics: Enqueued Transport Messages Per Second | The number of messages per second that have been placed onto the queues in the instance, counting only messages that arrived through the network. This counter is polled every fifteen minutes. | Microsoft.SQLServer.2016.SQLServer_Broker_Statistics_Enqueued_Transport_Msgs_sec_15.0_minutes_5_Rule | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Broker Statistics | Enqueued Transport Msgs/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Broker Statistics: SQL RECEIVEs Per Second | The number of SQL Server messages received per second. This counter is polled every fifteen minutes. | Microsoft.SQLServer.2016.SQLServer_Broker_Statistics_SQL_RECEIVEs_sec_15.0_minutes_5_Rule | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Broker Statistics | SQL RECEIVEs/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Broker Statistics: SQL SENDs Per Second | This counter displays the number of SQL Server messages sent per second. This counter is polled every fifteen minutes. | Microsoft.SQLServer.2016.SQLServer_Broker_Statistics_SQL_SENDs_sec_15.0_minutes_5_Rule | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Broker Statistics | SQL SENDs/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Broker Transport: Message Fragment Receives Per Second | This counter displays the number of message fragments received per second. This counter is polled every fifteen minutes. | Microsoft.SQLServer.2016.SQLServer_Broker_Transport_Message_Fragment_Receives_sec_15.0_minutes_5_Rule | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Broker/DBM Transport | Message Fragment Receives/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Broker Transport: Message Fragment Sends Per Second | This counter displays the number of message fragment sent per second. This counter is polled every fifteen minutes. | Microsoft.SQLServer.2016.SQLServer_Broker_Transport_Message_Fragment_Sends_sec_15.0_minutes_5_Rule | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Broker/DBM Transport | Message Fragment Sends/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Broker Transport: Open Connection Count | This counter displays the number of open SQL Server Broker connections. This counter is polled every fifteen minutes. | Microsoft.SQLServer.2016.SQLServer_Broker_Transport_Open_Connection_Count_15.0_minutes_5_Rule | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Broker/DBM Transport | Open Connection Count | 900 | 0 | | False | | | True | |
| MSSQL 2016: Broker Transport: Receive I/Os Per Second | This counter displays the number of I/Os received per second. This counter is polled every fifteen minutes. | Microsoft.SQLServer.2016.SQLServer_Broker_Transport_Receive_I_Os_sec_15.0_minutes_5_Rule | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Broker/DBM Transport | Receive I/Os/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Broker Transport: Send I/Os Per Second | This counter reports the number of transport send I/O operations per second that have completed. This counter is polled every fifteen minutes. | Microsoft.SQLServer.2016.SQLServer_Broker_Transport_Send_I_Os_sec_15.0_minutes_5_Rule | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Broker/DBM Transport | Send I/Os/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: SQL Server Assertion | SQL Server has raised an error. Under normal circumstances, SQL Server has posted a dump file in the log directory to help identify the actions that preceded the error. The error may have been caused by data corruption, an error in the client application, an error in SQL Server, network instability, or hardware failure. | Microsoft.SQLServer.2016.SQL_Server_Assertion_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 17066 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: SQL Server Assertion | SQL Server has raised an error. Under normal circumstances, SQL Server has posted a dump file in the log directory to help identify the actions that preceded the error. The error may have been caused by data corruption, an error in the client application, an error in SQL Server, network instability, or hardware failure. | Microsoft.SQLServer.2016.SQL_Server_Assertion_2_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 17067 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: SQL Server Assertion | SQL Server has raised an error. Under normal circumstances, SQL Server has posted a dump file in the log directory to help identify the actions that preceded the error. The error may have been caused by data corruption, an error in the client application, an error in SQL Server, network instability, or hardware failure. | Microsoft.SQLServer.2016.SQL_Server_Assertion_3_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 17065 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: SQL Server cannot start the Service Broker event handler | SQL Server Service Broker cannot start the Service Broker event handler. | Microsoft.SQLServer.2016.SQL_Server_cannot_start_the_Service_Broker_event_handler_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 9696 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: SQL Server could not allocate enough memory to start Service Broker task manager | SQL Server Service Broker cannot start Service Broker task manager. | Microsoft.SQLServer.2016.SQL_Server_could_not_allocate_enough_memory_to_start_Service_Broker_task_manager_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 9695 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: SQL Server Service Broker cannot use RC4 encryption algorithm when running in FIPS compliance mode | SQL Server Service Broker has a conversation where at least one endpoint has been configured to use RC4 encryption and the server is set for Federal Information Processing Standard (FIPS) compliance mode. RC4 encryption is not supported when running in FIPS compliance mode. | Microsoft.SQLServer.2016.SQL_Server_Service_Broker_cannot_use_RC4_encryption_algorithm_when_running_in_FIPS_compliance_mode_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 28078 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: SQL Server Service Broker could not query the FIPS compliance mode flag from the registry | The rule triggers an alert when SQL Server Service Broker could not query the FIPS compliance mode flag from the registry. | Microsoft.SQLServer.2016.SQL_Server_Service_Broker_could_not_query_the_FIPS_compliance_mode_flag_from_the_registry_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 28076 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: SQL Server Service Broker Manager has shutdown | The rule triggers an alert when the SQL Server Service Broker Manager has shutdown. Note: This rule is disabled by default. Please use overrides to enable it when necessary. | Microsoft.SQLServer.2016.SQL_Server_Service_Broker_Manager_has_shutdown_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | False | | | 0 | 9689 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Information | Normal | True | Application |
| MSSQL 2016: SQL Server Service Broker or Database Mirroring is running in FIPS compliance mode | The rule triggers an alert when SQL Server Service Broker or Database Mirroring is running in FIPS compliance mode. Note: This rule is disabled by default. Please use overrides to enable it when necessary. | Microsoft.SQLServer.2016.SQL_Server_Service_Broker_or_Database_Mirroring_is_running_in_FIPS_compliance_mode_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | False | | | 0 | 28077 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Information | Low | True | Application |
| MSSQL 2016: SQL Server Service Broker or Database Mirroring Transport stopped | The rule triggers an alert when at least one of the endpoints in a SQL Server Service Broker conversation has stopped listening for connections. Note: This rule is disabled by default. Please use overrides to enable it when necessary. | Microsoft.SQLServer.2016.SQL_Server_Service_Broker_or_Database_Mirroring_Transport_stopped_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | False | | | 0 | 9691 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Low | True | Application |
| MSSQL 2016: SQL Server Service Broker or Database Mirror cryptographic call failed | SQL Server Service Broker or Database Mirror attempted to call an operating system cryptographic function. The cryptographic function returned an error. | Microsoft.SQLServer.2016.SQL_Server_Service_Broker_or_Database_Mirror_cryptographic_call_failed_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 9650 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: SQL Server Service Broker transmitter shut down due to an exception or a lack of memory | The rule triggers an alert when SQL Server Service Broker transmitter stopped due to an error or a lack of memory. Note: This rule is disabled by default. Please use overrides to enable it when necessary. | Microsoft.SQLServer.2016.SQL_Server_Service_Broker_transmitter_shut_down_due_to_an_exception_or_a_lack_of_memory_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | False | | | 0 | 28073 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: SQL Server shutdown due to Ctrl-C or Ctrl-Break signal | The SQL Server instance was started from a command prompt using sqlservr.exe, and now a Ctrl-C or Ctrl-Break command was issued from that prompt to stop the sqlservr.exe application. No checkpoints were performed during the shutdown. This message is written to the SQL Server error log and the application event log. | Microsoft.SQLServer.2016.SQL_Server_shutdown_due_to_Ctrl_C_or_Ctrl_Break_signal_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 17676 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: SQL Server Service Broker attempted to use an unsupported encryption algorithm | The rule triggers an alert when SQL Server Service Broker tries to use an unsupported encryption algorithm. | Microsoft.SQLServer.2016.SQL_Server_SQL_Server_Service_Broker_attempted_to_use_an_unsupported_encryption_algorithm_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 28060 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: SQL Server terminating because of system shutdown | SQL Server is shutting down because the server is shutting down. Note: This rule is disabled by default. Please use overrides to enable it when necessary. | Microsoft.SQLServer.2016.SQL_Server_terminating_because_of_system_shutdown_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | False | | | 0 | 17147 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Starting without recovery | SQL Server is starting without recovery. | Microsoft.SQLServer.2016.Starting_without_recovery_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 17660 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Step of a job caused an exception in the subsystem | A specific job step caused SQL Server Agent to write an error to the Windows Application log. The log will show the specific job and job step. | Microsoft.SQLServer.2016.Step_of_a_job_caused_an_exception_in_the_subsystem_1_5_Rule | Microsoft.SQLServer.2016.Agent | EventCollection | True | | | 0 | 209 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.Agent"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Table error: Allocation page has invalid page header values. | The page specified has an invalid page header. | Microsoft.SQLServer.2016.Table_error__Allocation_page_has_invalid__page_header_values.__1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8946 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Table error: B-tree chain linkage mismatch. | There is a break in the logical page chain at some level in the B-tree specified (this can happen at any level, including the leaf level). A page P_ID2 is pointed to by the next page pointer of page P_ID1, but page P_ID2's previous page pointer points to a different page, P_ID3. | Microsoft.SQLServer.2016.Table_error__B_tree_chain_linkage_mismatch.__1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8936 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Table error: B-tree level mismatch, page does not match level from parent | There are two pages linked as parent (P_ID2) and child (P_ID1) in a B-tree. The level (LEVEL1) in the child page (P_ID1) does not comply with the level rules for B-trees, given the level (LEVEL2) in the parent page (P_ID2). | Microsoft.SQLServer.2016.Table_error__B_tree_level_mismatch_page_does_not_match_level_from_parent__1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8931 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Table error: B-tree page has two parent nodes | The B-tree structure is corrupt because page P_ID1 is referenced as a child page by slots in two pages higher in the B-tree, P_ID2 and P_ID3. A page can only be referenced by a single parent. | Microsoft.SQLServer.2016.Table_error__B_tree_page_has_two_parent_nodes__1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8937 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Table error: Column is not a valid complex column | A column is marked as being a complex column in the record's variable length column section, but it is not a valid text pointer or in-row text root. | Microsoft.SQLServer.2016.Table_error__Column_is_not_a_valid_complex_column_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8960 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Table error: cross-object chain linkage | The first phase of a DBCC CHECKDB is to do primitive checks on the data pages of critical system tables. If any errors are found, they cannot be repaired and so the DBCC CHECKDB terminates immediately. | Microsoft.SQLServer.2016.Table_error__cross_object_chain_linkage_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8930 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Table error: Cross object linkage. Page PGID->next is not in the same index | Page P_ID is linked to page P_ID2 but the two pages are allocated to different indexes and/or objects. | Microsoft.SQLServer.2016.Table_error__Cross_object_linkage._Page_PGID_next_is_not_in_the_same_index_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8982 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Table error: Cross object linkage | The page P_ID1 points, in a parent-child manner, to a page (P_ID2) in a different object. | Microsoft.SQLServer.2016.Table_error__Cross_object_linkage_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8925 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Table error: Cross object linkage: Parent page in object next refer to page not in the same object | The next page pointer of page P_ID2 and a child page pointer of page P_ID1 in a B-tree of the specified object points to a page (P_ID3) in a different object. Furthermore, pages P_ID1 and P_ID2 may themselves be in different objects. | Microsoft.SQLServer.2016.Table_error__Cross_object_linkage__Parent_page_in_object_next_refer_to_page_not_in_the_same_object_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8926 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Table error: Extent object is beyond the range of this database | P_ID is a PageID of the form (filenum:pageinfile). The pageinfile of this extent is greater than the physical size of the file filenum of the database. The extent is marked allocated in an IAM page for the object/index ID indicated. | Microsoft.SQLServer.2016.Table_error__Extent_object_is_beyond_the_range_of_this_database_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 2579 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Table error: Extra or invalid key | Every data row in a table (heap or clustered index) must have exactly one matching index row in every non-clustered index over that table. This error means that a non-clustered index has an index row that does not match any data row. | Microsoft.SQLServer.2016.Table_error__Extra_or_invalid_key_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8952 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Table error: IAM chain linkage error | There is a break in the IAM chain for the index specified. A page P_ID2 is pointed to by the next page pointer of page P_ID1, but page P_ID2's previous page pointer points to a different page, P_ID3. Both error states mean the same, and only differ in where the corruption was discovered. | Microsoft.SQLServer.2016.Table_error__IAM_chain_linkage_error_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8969 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Table error: IAM page is linked in the IAM chain for object | All IAM pages for an index must have the same index ID on them. In this case, one of the IAM pages linked into the IAM chain for index I_ID2 has index ID I_ID1 on it. There are three possible states of this error; they all mean the same thing, but differ in where the discovery is made. | Microsoft.SQLServer.2016.Table_error__IAM_page_is_linked_in_the_IAM_chain_for_object_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8959 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Table error: Index node page refers to child page and previous child, but they were not encountered | An index page (P_ID1) in a B-tree has child references to two neighboring lower-level pages (P_ID2 and P_ID3), but neither was seen. | Microsoft.SQLServer.2016.Table_error__Index_node_page_refers_to_child_page_and_previous_child_but_they_were_not_encountered_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8980 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Table error: Object, index, page Test failed. Slot - Offset is invalid | The slot specified has an invalid offset (ADDRESS) in the page, according to the slot array. | Microsoft.SQLServer.2016.Table_error__Object_index_page_Test_failed._Slot___Offset_is__invalid_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8941 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Table error: Page allocated to object was not seen. Page may be invalid or have incorrect object ID information in its header | A page is allocated as specified, but was not seen with that object/index ID in its header. The page has a different index ID in its header, so there will be a matching 2534 (page allocated by another object) error for the page. The 2534 error corresponds to the object/index ID that is in the page's header. | Microsoft.SQLServer.2016.Table_error__Page_allocated_to_object_was_not_seen.__Page_may_be_invalid_or_have_incorrect_object_ID_information_in_its_header_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 2533 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Table error: Page in its header is allocated by another object | A page has the object/index ID specified but is not allocated by any of that index's IAM pages. The page has an incorrect object/index ID in its header, so there will be a matching 2533 (page not seen although allocated) error for the page. The 2533 error corresponds to the index the page is really allocated to. | Microsoft.SQLServer.2016.Table_error__Page_in_its_header_is_allocated_by_another_object_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 2534 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Table error: Page is missing a reference from previous page. Possible chain linkage problem | A page (P_ID2) in a B-tree was not seen, even though its neighbor (P_ID1) in the page chain points to it in its previous page link. This can happen in any level of the B-tree. Both error states mean the same thing; they differ only in where the error is discovered. | Microsoft.SQLServer.2016.Table_error__Page_is_missing_a_reference_from_previous_page._Possible_chain_linkage_problem_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8978 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Table error: Page is missing references from parent (unknown) and previous nodes. Possible bad root entry in sysindexes | Page P_ID1 was seen, but is not linked into the B-tree it thinks it belongs to. | Microsoft.SQLServer.2016.Table_error__Page_is_missing_references_from_parent__unknown__and_previous_nodes._Possible_bad_root_entry_in_sysindexes_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8979 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Table error: page is out of the range of this database | The page specified is marked as allocated, but is beyond the in-use portion of the file in which it resides (except in certain states, as described below). | Microsoft.SQLServer.2016.Table_error__page_is_out_of_the_range_of_this_database_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8968 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Table error: Page was not seen in the scan although its parent and previous refer to it. Check any previous errors | A page (P_ID1) in a B-tree was not seen, even though an index page (P_ID2) points to it as a child page and its previous page (P_ID3) in the page chain points to it as the next page in the chain. This can happen at any level of the B-tree. Both error states mean the same thing; they differ only in where the error was discovered. | Microsoft.SQLServer.2016.Table_error__Page_was_not_seen_in_the_scan_although_its_parent_and_previous_refer_to_it._Check_any_previous_errors_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8976 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Table error: Parent node for page was not encountered | Page P_ID was seen in a B-tree, and is linked into the B-tree level it is at. However, no index page was seen that had a reference to the page as a child page. This can happen at any level of the B-tree. | Microsoft.SQLServer.2016.Table_error__Parent_node_for_page_was_not_encountered_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8977 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Table error: Slot, row extends into free space | The end of the slot S_ID is past the persisted free space offset, ADDRESS. TEST is 'max <= m_freeData', where the persisted free space offset if 'm_freeData' and the end of slot S_ID is 'max'. | Microsoft.SQLServer.2016.Table_error__Slot_row_extends_into_free_space__1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8943 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Table error: Table missing or invalid key in index for the row: | Every data row in a table (heap or clustered index) must have exactly one matching index row in every non-clustered index over that table. This error means that a non-clustered index is missing an index row. | Microsoft.SQLServer.2016.Table_error__Table_missing_or_invalid_key_in_index_for_the_row__1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8951 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Table error: The high key value on page is not less than the low key value in the parent, slot of the next page | A B-tree tree-level page contains a record for each child page, along with a key value for that child page. If the child page is a leaf-level page, all records on the page must have key values greater than or equal to the key value in the parent page. If the child page is a tree-level page, all records must have key values greater than the key value in the parent, except the first record, which must have a key value that exactly matches that in the parent. | Microsoft.SQLServer.2016.Table_error__The_high_key_value_on_page_is_not_less_than_the_low_key_value_in_the_parent_slot_of_the_next_page_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8934 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Table error: The low key value on page is not the key value in the parent | A B-tree tree level page contains a record for each child page, along with a key value for that child page. If the child page is a leaf-level page (that is, level 0), all records on the page must have key values greater than or equal to the key value in the parent page. If the child page is a tree-level page (that is, level > 0), all records must have key values greater than the key value in the parent, except the first record, which must have a key value that exactly matches that in the parent. | Microsoft.SQLServer.2016.Table_error__The_low_key_value_on_page__is_not_the_key_value_in_the_parent_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8933 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Table error: The previous link on page does not match the previous page that the parent, slot expects for this page | A B-tree is structured so that pages at a single level point to each other, in a doubly-linked list. Also, the pages' parent in the B-tree has a record for each of its children, with their keys and page IDs. | Microsoft.SQLServer.2016.Table_error__The_previous_link_on_page_does_not_match_the_previous_page_that_the_parent_slot_expects_for_this_page_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8935 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Table error: The text, ntext, or image node at page is not referenced | The text node was not referenced in any complex column in any heap or clustered index. It is effectively orphaned. | Microsoft.SQLServer.2016.Table_error__The_text_ntext_or_image_node_at_page_is_not_referenced_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8964 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Table error: The text, ntext, or image node at page is referenced by page not seen in the scan | The text node was not referenced in any complex column in any heap or clustered index. It is effectively orphaned. | Microsoft.SQLServer.2016.Table_error__The_text_ntext_or_image_node_at_page__is_referenced_by_page_not_seen_in_the_scan_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8965 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Table error: The text, ntext, or image node has wrong type | The text node is on the wrong text page type. If the parent (owner) of the node can be found, there will be an accompanying 8929 message providing details about the owner. | Microsoft.SQLServer.2016.Table_error__The_text_ntext_or_image_node_has_wrong_type_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8963 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Table error: Wrong PageId in the page header | DBCC asked for page P_ID1. When the page was read from disk, the page ID in its header was found to be P_ID2. | Microsoft.SQLServer.2016.Table_error__Wrong_PageId_in_the_page_header_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8909 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Table error: Address is not aligned | The structure at address ADDRESS is not 4-byte aligned. | Microsoft.SQLServer.2016.Table_error___Address_is_not_aligned_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8940 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Table error: Test failed. Slot overlaps with the prior row | Slot S_ID's offset in the slot offset array is not greater than or equal to the end of the previous slot, so they overlap. TEST is 'sorted [i].offset >= max', where the lhs of the expression is the ADDRESS, and 'max' is the end of the previous slot. | Microsoft.SQLServer.2016.Table_error___Test_failed._Slot_overlaps_with_the_prior_row_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8942 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Table error: The next pointer of refers to page. Neither its parent were encountered. Possible bad chain linkage | A page (P_ID1) references its next page in the page chain (P_ID2), but page P_ID2 was not seen and was not referenced by any parent page in the B-tree. | Microsoft.SQLServer.2016.Table_error___The_next_pointer_of_refers_to_page._Neither_its_parent_were_encountered._Possible_bad_chain_linkage_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8981 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Table error: Unexpected page type | Page P_ID had a page type that was unexpected by the code trying to interpret it. The page is marked allocated, however, which is why the DBCC code is trying to interpret it. | Microsoft.SQLServer.2016.Table_error___Unexpected_page_type__1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8938 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Table: Creating statistics for the following columns | sp_createstats has generated statistics for each eligible column in the current database. Computed columns and columns of the ntext, text, or image data types cannot be specified as statistics columns. Columns already having statistics are not touched (for example, the first column of an index or a column with explicitly created statistics). Note: This rule is disabled by default. Please use overrides to enable it when necessary. | Microsoft.SQLServer.2016.Table__Creating_statistics_for_the_following_columns_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | False | | | 0 | 15018 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: Table: No columns without statistics found | There are no eligible columns in the current database on which to create statistics using sp_createstats . Computed columns and columns of the ntext, text, or image data types cannot be specified as statistics columns. Columns already having statistics are not touched (for example, the first column of an index or a column with explicitly created statistics). | Microsoft.SQLServer.2016.Table___No_columns_without_statistics_found_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 15013 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: The agent is suspect. No response within last minutes | This behavior occurs because the replication agent is too busy to respond when SQL Server Enterprise Manager polls the replication agent; therefore, SQL Server Enterprise Manager does not know the status of the replication agent and it cannot report whether the replication agent is functioning or not. | Microsoft.SQLServer.2016.The_agent_is_suspect._No_response_within_last_minutes_1_5_Rule | Microsoft.SQLServer.2016.Agent | EventCollection | True | | | 0 | 20554 | $Target/Host/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: The I/O operation was successful after retry | A read operation on a database page or transaction log block was successful but only after retrying the operation. While you may not need to take immediate action, you should research the cause of the error. | Microsoft.SQLServer.2016.The_IO_operation_was_successful_after_retry_id825 | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 825 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: The log for database is not available | An I/O error related to data integrity has occurred for the specified database. Either the log or data portion of the database could be damaged. SQL Server has made the log for that database unavailable to prevent further data integrity problems. The I/O error that led to the 9001 message should be reported in the SQL Server error log and/or the Windows event logs. | Microsoft.SQLServer.2016.The_log_for_database_is_not_available_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 9001 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: The LSN passed to log scan in database is invalid | If you see this message during startup when the SQL Server process tries to recover the database or as a result of an ATTACH statement, the log file for the database is corrupted. If you see the message during a restore process, the backup file is corrupted. If you see this message during a replication process, the replication metadata may be incorrect. | Microsoft.SQLServer.2016.The_LSN_passed_to_log_scan_in_database_is_invalid_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 9003 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: The MSSQLServer service terminated unexpectedly | The error is reported by the SQL Server Agent service when it auto restarts SQL Server. SQL Server Agent will only auto restart SQL Server if SQL Server stopped for some reason other than an explicit stop command from a user or application, and if the Auto restart SQL Server if it stops unexpectedly option is selected in SQL Server Agent Advanced properties. During the restart of SQL Server, SQL Server Agent will write this message to the application event log on the computer hosting SQL Server. | Microsoft.SQLServer.2016.The_MSSQLServer_service_terminated_unexpectedly_3_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 14265 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: The provider reported an unexpected catastrophic failure | The provider reported an unexpected catastrophic failure. | Microsoft.SQLServer.2016.The_provider_reported_an_unexpected_catastrophic_failure_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 10001 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: The query has been canceled because the estimated cost of this query exceeds the configured threshold. Contact the system administrator | The configuration setting for the query governor cost limit option is lower than the cost the SQL Server optimizer estimated for the specified query. By default, the query governor cost limit option is set to 0, which allows all queries to run. However, on this instance of SQL Server an upper limit was specified by setting the option to a number greater than 0. Query plans with an anticipated cost larger than this value are not started. | Microsoft.SQLServer.2016.The_query_has_been_canceled_because_the_estimated_cost_of_this_query_exceeds_the_configured_threshold._Contact_the_system_administrator_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8649 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: The query processor could not start the necessary thread resources for parallel query execution | Thread resources are scarce in the server. | Microsoft.SQLServer.2016.The_query_processor_could_not_start_the_necessary_thread_resources_for_parallel_query_execution_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 8642 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: The server is too busy to perform the backup or restore operation | Failed to start a sub-process (a parallel query or parallel I/O) because no threads are available or too many sub-processes executing. | Microsoft.SQLServer.2016.The_server_is_too_busy_to_perform_the_backup_or_restore_operation_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 3627 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: The Service Broker/Database Mirroring transport cannot listen on port because it is in use | When you create a Service Broker or Database Mirroring endpoint, SQL Server should be able to accept TCP/IP connections on the port that is specified in the endpoint configuration. The transport security requires authorization for connections to the port. If the server has a firewall enabled, the firewall configuration must allow both incoming and outgoing connections for the port that is used by the endpoint. | Microsoft.SQLServer.2016.The_Service_Broker_Database_Mirroring_transport_cannot_listen_on_port_because_it_is_in_use_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 9692 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: The Service Broker/Database Mirroring Transport could not listen for connections due to an error | The rule triggers an alert when Service Broker cannot listen on the specified port. | Microsoft.SQLServer.2016.The_Service_Broker_Database_Mirroring_Transport_could_not_listen_for_connections_due_to_an_error_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 9693 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: The Service Broker or Database Mirroring Transport has started | SQL Server Service Broker or Database Mirroring transport has started. The Windows application log specifies whether the error was recorded by Service Broker or Database Mirroring the application name. This message is logged in the Windows application log as MSSQLSERVER event ID 9690. Note: This rule is disabled by default. Please use overrides to enable it when necessary. | Microsoft.SQLServer.2016.The_Service_Broker_or_Database_Mirroring_Transport_has_started_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | False | | | 0 | 9690 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Information | Low | True | Application |
| MSSQL 2016: The SQL Server Service Broker or Database Mirroring transport is disabled or not configured | The rule triggers an alert when the SQL Server Service Broker or Database Mirroring transport is disabled or not configured. Note: This rule is disabled by default. Please use overrides to enable it when necessary. | Microsoft.SQLServer.2016.The_SQL_Server_Service_Broker_or_Database_Mirroring_transport_is_disabled_or_not_configured_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | False | | | 0 | 9666 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | High | True | Application |
| MSSQL 2016: The user is not allowed to truncate the system table | The TRUNCATE TABLE statement cannot be issued for a system table, even if the allow updates configuration option is enabled. | Microsoft.SQLServer.2016.The_user_is_not_allowed_to_truncate_the_system_table_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 4709 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Total Transactions Per Second | Collects the Windows "Transaction Per Second" performance counter for the _Total instance of the databases performance object for each instance of SQL 2016 DB Engine. | Microsoft.SQLServer.2016.TransactionsPerSecond | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:Databases | Transactions/sec | 900 | 0 | | False | | | True | |
| MSSQL 2016: Transaction was deadlocked on resources with another process and has been chosen as the deadlock victim. Rerun the transaction | This error occurs when Microsoft SQL Server encounters a deadlock. A deadlock occurs when two (or more) processes attempt to access a resource that the other process holds a lock on. Because each process has a request for another resource, neither process can be completed. When a deadlock is detected, SQL Server rolls back the command that has the least processing time and returns error message 1205 to the client application. This error is not fatal and may not cause the batch to be terminated. | Microsoft.SQLServer.2016.Transaction_was_deadlocked_on_resources_with_another_process_and_has_been_chosen_as_the_deadlock_victim._Rerun_the_transaction_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 1205 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: : SQL Server Agent is unable to connect to SQL Server | The SQL Server Agent Service could not connect to the instance of SQL Server. This error may occur when the SQL Server Agent service account does not have a valid login on SQL Server | Microsoft.SQLServer.2016.Unable_to_connect_to_SQL_Server_1_5_Rule | Microsoft.SQLServer.2016.Agent | EventCollection | True | | | 0 | 207 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.Agent"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Unable to re-open the local eventlog | SQL Server Agent was unable to open the local event log. | Microsoft.SQLServer.2016.Unable_to_re_open_the_local_eventlog_1_5_Rule | Microsoft.SQLServer.2016.Agent | EventCollection | True | | | 0 | 313 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.Agent"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Unexpected end of file while reading beginning of backup set | The RESTORE operation failed because it could not read some portion of the backup file specified in the FROM clause. This error generally indicates that the file specified is a pre-SQL Server 7.0 backup or that the file is damaged. | Microsoft.SQLServer.2016.Unexpected_end_of_file_while_reading_beginning_of_backup_set_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 3208 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: Unique table computation failed | Unique tables are used by the database client drivers, like Microsoft Access driver for SQL Server, to build updateable queries. For a given SELECT statement, the unique table identifies the table whose row values appear at most once in the result set. When reselecting a row from a result set, the values from the key columns of the unique table are enough to identify the row. This error is raised when the server is unable to compute the unique table. | Microsoft.SQLServer.2016.Unique_table_computation_failed_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 16959 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: SQL User Connections | Counts the number of users currently connected to SQL Server. | Microsoft.SQLServer.2016.UserConnectionsCollection | Microsoft.SQLServer.2016.DBEngine | PerformanceCollection | True | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/PerformanceCounterObject$:General Statistics | User Connections | 900 | 0 | | False | | | True | |
| MSSQL 2016: XML : Failed to instantiate class. Make sure Msxml2.dll exists in the SQL Server installation | The Msxml2.dll file is missing from the computer where SQL Server is installed, or it could not be loaded from the system directory while processing an XML feature such as sp_xml_preparedocument . If the file exists, it may not be registered properly, or one of its dependencies may not exist. | Microsoft.SQLServer.2016.XML___Failed_to_instantiate_class._Make_sure_Msxml2.dll_exists_in_the_SQL_Server_installation_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 6608 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: XML : Failed to load Msxml2.dll | The Msxml2.dll file is missing from the computer where SQL Server is installed, or it could not be loaded from the system directory while processing an XML feature such as sp_xml_preparedocument . If the file exists, it may not be registered properly, or one of its dependencies may not exist. | Microsoft.SQLServer.2016.XML___Failed_to_load_Msxml2.dll_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 6610 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: XML : FOR XML EXPLICIT stack overflow occurred. Circular parent tag relationships are not allowed | The XML is not well-formed because the element tag nesting level has exceeded the number of columns in the table, one or more tags is self-referencing, or both. For more information about FOR XML EXPLICIT, see "Using EXPLICIT Mode" in Books Online. | Microsoft.SQLServer.2016.XML___FOR_XML_EXPLICIT_stack_overflow_occurred._Circular_parent_tag_relationships_are_not_allowed_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 6805 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: XML : Size of data chunk requested from the stream exceeds allowed limit | SQL Server received an XML document that exceeds the allowed limit. | Microsoft.SQLServer.2016.XML___Size_of_data_chunk_requested_from_the_stream_exceeds_allowed_limit_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 6627 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: XML : XML document could not be created because server memory is low. Use sp_xml_removedocument to release XML documents | When you execute sp_xml_preparedocument , a parsed XML document is stored in the internal cache of SQL Server 2000. The MSXML parser uses up to one-eighth the total memory available for SQL Server. There is not enough memory in the portion of cache allocated to MSXML to open the document specified in the sp_xml_preparedocument statement. This may be because the specified document is very large or because documents already in that memory space do not leave enough space for the new document. | Microsoft.SQLServer.2016.XML___XML_document_could_not_be_created_because_server_memory_is_low._Use_sp_xml_removedocument_to_release_XML_documents_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 6624 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: XML : XML error | This message passes through XML errors generated outside of SQL Server. The text after "XML error:" will vary. The cause will depend on the exact XML error passed through. | Microsoft.SQLServer.2016.XML___XML_error_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 6600 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Warning | Normal | True | Application |
| MSSQL 2016: XML : XML parsing error | This message passes through XML parsing errors. The text after "XML parsing error:" will vary. The cause will depend on the exact XML parsing error passed through. | Microsoft.SQLServer.2016.XML___XML_parsing_error_1_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 6603 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
| MSSQL 2016: .NET Framework runtime was shut down by user code | The rule triggers an alert when a user defined type, user defined-function, or user-defined property in an assembly contains faulty code. | Microsoft.SQLServer.2016._.NET_Framework_runtime_was_shut_down_by_user_code_5_Rule | Microsoft.SQLServer.2016.DBEngine | EventCollection | True | | | 0 | 6537 | $Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$ | True | Error | Normal | True | Application |
Home