All Rules in Microsoft.SQLServer.Linux.Monitoring Management Pack

 DisplayNameDescriptionIDTargetCategoryEnabledInstance NameCounter NameFrequencyEvent_IDEvent SourceAlert GenerateAlert SeverityAlert PriorityRemotableEvent Log
Microsoft.SQLServer.Linux.CollectionRule.Agent.Alert_engine_stopped_due_to_unrecoverable_local_eventlog_errors_1_5_RuleMSSQL on Linux: Alert engine stopped due to unrecoverable local eventlog errorsSQL Server Agent was unable to open the local event log.Microsoft.SQLServer.Linux.CollectionRule.Agent.Alert_engine_stopped_due_to_unrecoverable_local_eventlog_errors_1_5_RuleMicrosoft.SQLServer.Linux.AgentEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.CollectionRule.Agent.A_SQL_job_failed_to_complete_successfully_1_5_RuleMSSQL on Linux: A SQL job failed to complete successfullyA 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.Linux.CollectionRule.Agent.A_SQL_job_failed_to_complete_successfully_1_5_RuleMicrosoft.SQLServer.Linux.AgentEventCollectionFalse00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.CollectionRule.Agent.Job_step_cannot_be_run_because_the_subsystem_failed_to_load_1_5_RuleMSSQL on Linux: Job step cannot be run because the subsystem failed to loadA SQL Server job failed to run because the SQL Server Agent subsystem failed to load.Microsoft.SQLServer.Linux.CollectionRule.Agent.Job_step_cannot_be_run_because_the_subsystem_failed_to_load_1_5_RuleMicrosoft.SQLServer.Linux.AgentEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.CollectionRule.Agent.SQLServerAgent_could_not_be_started_1_5_RuleMSSQL on Linux: SQL Server Agent could not be startedA process or a person attempted to start the SQL Server Agent service, but the service did not start.Microsoft.SQLServer.Linux.CollectionRule.Agent.SQLServerAgent_could_not_be_started_1_5_RuleMicrosoft.SQLServer.Linux.AgentEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.CollectionRule.Agent.SQLServerAgent_initiating_self_termination_1_5_RuleMSSQL on Linux: SQL Server Agent initiating self-terminationSQL Server Agent has shut down the SQL Server Agent service.Microsoft.SQLServer.Linux.CollectionRule.Agent.SQLServerAgent_initiating_self_termination_1_5_RuleMicrosoft.SQLServer.Linux.AgentEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.CollectionRule.Agent.Step_of_a_job_caused_an_exception_in_the_subsystem_1_5_RuleMSSQL on Linux: Step of a job caused an exception in the subsystemA specific job step caused SQL Server Agent to write an error to the Linux Application log. The log will show the specific job and job step.Microsoft.SQLServer.Linux.CollectionRule.Agent.Step_of_a_job_caused_an_exception_in_the_subsystem_1_5_RuleMicrosoft.SQLServer.Linux.AgentEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.CollectionRule.Agent.The_agent_is_suspect._No_response_within_last_minutes_1_5_RuleMSSQL on Linux: The agent is suspect. No response within last minutesThis 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.Linux.CollectionRule.Agent.The_agent_is_suspect._No_response_within_last_minutes_1_5_RuleMicrosoft.SQLServer.Linux.AgentEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.CollectionRule.Agent.Unable_to_connect_to_SQL_Server_1_5_RuleMSSQL on Linux: SQL Server Agent is unable to connect to SQL ServerThe 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 ServerMicrosoft.SQLServer.Linux.CollectionRule.Agent.Unable_to_connect_to_SQL_Server_1_5_RuleMicrosoft.SQLServer.Linux.AgentEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.CollectionRule.Agent.Unable_to_re_open_the_local_eventlog_1_5_RuleMSSQL on Linux: Unable to re-open the local eventlogSQL Server Agent was unable to open the local event log.Microsoft.SQLServer.Linux.CollectionRule.Agent.Unable_to_re_open_the_local_eventlog_1_5_RuleMicrosoft.SQLServer.Linux.AgentEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.CollectionRule.AvailabilityReplica.BytesReceivedFromReplicaPerSecondMSSQL on Linux: Bytes Received from Replica / secTotal number of bytes received from this replica over the network for the AG.Microsoft.SQLServer.Linux.CollectionRule.AvailabilityReplica.BytesReceivedFromReplicaPerSecondMicrosoft.SQLServer.Linux.AvailabilityReplicaPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.AvailabilityReplica.BytesSentToReplicaPerSecondMSSQL on Linux: Bytes Sent to Replica / secThe number of database message bytes enqueued to be send over the network to this replica. The bytes include messages for all databases in the AG.Microsoft.SQLServer.Linux.CollectionRule.AvailabilityReplica.BytesSentToReplicaPerSecondMicrosoft.SQLServer.Linux.AvailabilityReplicaPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.AvailabilityReplica.BytesSentToTransportPerSecondMSSQL on Linux: Bytes Sent to Transport / secThe total number of bytes send over the network to the replica.Microsoft.SQLServer.Linux.CollectionRule.AvailabilityReplica.BytesSentToTransportPerSecondMicrosoft.SQLServer.Linux.AvailabilityReplicaPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.AvailabilityReplica.FlowControlPerSecondMSSQL on Linux: Flow Control / secNumber of flow controls enabled for this replica per second.Microsoft.SQLServer.Linux.CollectionRule.AvailabilityReplica.FlowControlPerSecondMicrosoft.SQLServer.Linux.AvailabilityReplicaPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.AvailabilityReplica.FlowControlTimeSecondsMSSQL on Linux: Flow Control Time (ms/sec)The number of milliseconds flow control was enabled to this replica within the last second.Microsoft.SQLServer.Linux.CollectionRule.AvailabilityReplica.FlowControlTimeSecondsMicrosoft.SQLServer.Linux.AvailabilityReplicaPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.AvailabilityReplica.ReceivesFromReplicaPerSecondMSSQL on Linux: Receives from Replica / secTotal number of messages received from this replica for the AG.Microsoft.SQLServer.Linux.CollectionRule.AvailabilityReplica.ReceivesFromReplicaPerSecondMicrosoft.SQLServer.Linux.AvailabilityReplicaPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.AvailabilityReplica.ResentMessagesPerSecondMSSQL on Linux: Resent Messages / secThe rate per second to get acknowledgements for messages sent to the replica.Microsoft.SQLServer.Linux.CollectionRule.AvailabilityReplica.ResentMessagesPerSecondMicrosoft.SQLServer.Linux.AvailabilityReplicaPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.AvailabilityReplica.SendsToReplicaPerSecondMSSQL on Linux: Sends to Replica / secNumber of messages enqueued to be send over the network to this replica.Microsoft.SQLServer.Linux.CollectionRule.AvailabilityReplica.SendsToReplicaPerSecondMicrosoft.SQLServer.Linux.AvailabilityReplicaPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.AvailabilityReplica.SendsToTransportPerSecondMSSQL on Linux: Sends to Transport / secNumber of messages sent over the network to this replica. This account for all the messages sent from this replica including control messages.Microsoft.SQLServer.Linux.CollectionRule.AvailabilityReplica.SendsToTransportPerSecondMicrosoft.SQLServer.Linux.AvailabilityReplicaPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.Container.SpaceFreeMBMSSQL on Linux: 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.Linux.CollectionRule.Container.SpaceFreeMBMicrosoft.SQLServer.Linux.ContainerPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.Container.SpaceFreePercentMSSQL on Linux: 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.Linux.CollectionRule.Container.SpaceFreePercentMicrosoft.SQLServer.Linux.ContainerPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.Database.ActiveTransactionsMSSQL on Linux: DB Active Transactions CountMSSQL on Linux DBs Active Transactions performance collection ruleMicrosoft.SQLServer.Linux.CollectionRule.Database.ActiveTransactionsMicrosoft.SQLServer.Linux.DatabasePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.Database.DBActiveConnectionsCountMSSQL on Linux: DB Active Connections CountSQL on Linux DBs Active Connections performance collection ruleMicrosoft.SQLServer.Linux.CollectionRule.Database.DBActiveConnectionsCountMicrosoft.SQLServer.Linux.DatabasePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.Database.DBActiveRequestsCountMSSQL on Linux: DB Active Requests CountSQL on Linux DBs Active Requests performance collection ruleMicrosoft.SQLServer.Linux.CollectionRule.Database.DBActiveRequestsCountMicrosoft.SQLServer.Linux.DatabasePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.Database.DBActiveSessionsCountMSSQL on Linux: DB Active Sessions CountSQL on Linux DBs Active Sessions performance collection ruleMicrosoft.SQLServer.Linux.CollectionRule.Database.DBActiveSessionsCountMicrosoft.SQLServer.Linux.DatabasePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.Database.DBDiskReadLatencyMSSQL on Linux: DB Disk Read Latency (ms)Collects maximum disk Read latency from all logical disks which host database files.Microsoft.SQLServer.Linux.CollectionRule.Database.DBDiskReadLatencyMicrosoft.SQLServer.Linux.DatabasePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.Database.DBDiskWriteLatencyMSSQL on Linux: DB Disk Write Latency (ms)Collects maximum disk Write latency from all logical disks which host database files.Microsoft.SQLServer.Linux.CollectionRule.Database.DBDiskWriteLatencyMicrosoft.SQLServer.Linux.DatabasePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.Database.TransactionsPerSecMSSQL on Linux: DB Transactions per Second CountSQL on Linux DBs Transactions per second performance collection ruleMicrosoft.SQLServer.Linux.CollectionRule.Database.TransactionsPerSecMicrosoft.SQLServer.Linux.DatabasePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DatabaseReplica.FileBytesReceivedPerSecondMSSQL on Linux: File Bytes Received / secAmount of FILESTREAM data received by the secondary replica for the secondary database in the last second.Microsoft.SQLServer.Linux.CollectionRule.DatabaseReplica.FileBytesReceivedPerSecondMicrosoft.SQLServer.Linux.DatabaseReplicaPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DatabaseReplica.LogApplyPendingQueueMSSQL on Linux: Log Apply Pending QueueNumber of log blocks pending to be applied to the database replica.Microsoft.SQLServer.Linux.CollectionRule.DatabaseReplica.LogApplyPendingQueueMicrosoft.SQLServer.Linux.DatabaseReplicaPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DatabaseReplica.LogApplyReadyQueueMSSQL on Linux: Log Apply Ready QueueNumber of log blocks pending and ready to be applied to the database replica.Microsoft.SQLServer.Linux.CollectionRule.DatabaseReplica.LogApplyReadyQueueMicrosoft.SQLServer.Linux.DatabaseReplicaPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DatabaseReplica.LogBytesReceivedPerSecondMSSQL on Linux: Log Bytes Received / secThe number of log bytes received by this replica. This is valid only on the secondary replica.Microsoft.SQLServer.Linux.CollectionRule.DatabaseReplica.LogBytesReceivedPerSecondMicrosoft.SQLServer.Linux.DatabaseReplicaPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DatabaseReplica.LogRemainingForUndoMSSQL on Linux: Log Remaining for undoThe amount of log that need to be undone in KB.Microsoft.SQLServer.Linux.CollectionRule.DatabaseReplica.LogRemainingForUndoMicrosoft.SQLServer.Linux.DatabaseReplicaPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DatabaseReplica.LogSendQueueMSSQL on Linux: Log Send QueueThe size of the log send queue on this replica.Microsoft.SQLServer.Linux.CollectionRule.DatabaseReplica.LogSendQueueMicrosoft.SQLServer.Linux.DatabaseReplicaPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DatabaseReplica.MirroredWriteTransactionsPerSecondMSSQL on Linux: Mirrored Write Transactions / secThe number of transactions processed through synchronization commits. Dividing transaction delay by mirrored transactions to get delay per transaction.Microsoft.SQLServer.Linux.CollectionRule.DatabaseReplica.MirroredWriteTransactionsPerSecondMicrosoft.SQLServer.Linux.DatabaseReplicaPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DatabaseReplica.RecoveryQueueMSSQL on Linux: Recovery QueueAmount of log records in the log files of the secondary replica that has not yet been redone.Microsoft.SQLServer.Linux.CollectionRule.DatabaseReplica.RecoveryQueueMicrosoft.SQLServer.Linux.DatabaseReplicaPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DatabaseReplica.RedoBlockedSecMSSQL on Linux: Redo blocked / secNumber of times the REDO thread was blocked in this database since this database was brought ONLINE.Microsoft.SQLServer.Linux.CollectionRule.DatabaseReplica.RedoBlockedSecMicrosoft.SQLServer.Linux.DatabaseReplicaPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DatabaseReplica.RedoBytesRemainingMSSQL on Linux: Redo Bytes RemainingThe amount of log bytes remaining to be redone to finish the reverting phase.Microsoft.SQLServer.Linux.CollectionRule.DatabaseReplica.RedoBytesRemainingMicrosoft.SQLServer.Linux.DatabaseReplicaPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DatabaseReplica.RedoneBytesPerSecondMSSQL on Linux: Redone Bytes / secThe rate at which log records are redone on the secondary replica.Microsoft.SQLServer.Linux.CollectionRule.DatabaseReplica.RedoneBytesPerSecondMicrosoft.SQLServer.Linux.DatabaseReplicaPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DatabaseReplica.TotalLogRequiringUndoMSSQL on Linux: Total Log requiring undoTotal kilobytes of log that must be undone.Microsoft.SQLServer.Linux.CollectionRule.DatabaseReplica.TotalLogRequiringUndoMicrosoft.SQLServer.Linux.DatabaseReplicaPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DatabaseReplica.TransactionDelayMSSQL on Linux: Transaction DelayThe total time for all transactions waited on the secondary acknowledgement.Microsoft.SQLServer.Linux.CollectionRule.DatabaseReplica.TransactionDelayMicrosoft.SQLServer.Linux.DatabaseReplicaPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.AverageWaitTimeMSSQL on Linux: DB Engine Average Wait Time (Milliseconds)SQL DB Engine on Linux Average Wait Time performance collection ruleMicrosoft.SQLServer.Linux.CollectionRule.DBEngine.AverageWaitTimeMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerActivation_StoredProceduresInvokedSecMSSQL on Linux: Broker Activation: Stored Procedures Invoked per SecondCollects the "Broker Activation: Stored Procedures Invoked per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerActivation_StoredProceduresInvokedSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerActivation_TaskLimitReachedMSSQL on Linux: Broker Activation: Task Limit ReachedCollects the "Broker Activation: Task Limit Reached" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerActivation_TaskLimitReachedMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerActivation_TaskLimitReachedSecMSSQL on Linux: Broker Activation: Task Limit Reached per SecondCollects the "Broker Activation: Task Limit Reached per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerActivation_TaskLimitReachedSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerActivation_TasksAbortedSecMSSQL on Linux: Broker Activation: Tasks Aborted per SecondCollects the "Broker Activation: Tasks Aborted per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerActivation_TasksAbortedSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerActivation_TasksRunningMSSQL on Linux: Broker Activation: Tasks RunningCollects the "Broker Activation: Tasks Running" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerActivation_TasksRunningMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerActivation_TasksStartedSecMSSQL on Linux: Broker Activation: Tasks Started per SecondCollects the "Broker Activation: Tasks Started per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerActivation_TasksStartedSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_CurrentBytesForRecvIOMSSQL on Linux: Broker/DBM Transport: Current Bytes for Receive I/OCollects the "Broker/DBM Transport: Current Bytes for Receive I/O" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_CurrentBytesForRecvIOMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_CurrentBytesForSendIOMSSQL on Linux: Broker/DBM Transport: Current Bytes for Send I/OCollects the "Broker/DBM Transport: Current Bytes for Send I/O" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_CurrentBytesForSendIOMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_CurrentMsgFragsForSendIOMSSQL on Linux: Broker/DBM Transport: Current Message Fragments for Send I/OCollects the "Broker/DBM Transport: Current Message Fragments for Send I/O" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_CurrentMsgFragsForSendIOMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_MessageFragmentP10SendsSecMSSQL on Linux: Broker/DBM Transport: Message Fragment P10 Sends per SecondCollects the "Broker/DBM Transport: Message Fragment P10 Sends per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_MessageFragmentP10SendsSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_MessageFragmentP1SendsSecMSSQL on Linux: Broker/DBM Transport: Message Fragment P1 Sends per SecondCollects the "Broker/DBM Transport: Message Fragment P1 Sends per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_MessageFragmentP1SendsSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_MessageFragmentP2SendsSecMSSQL on Linux: Broker/DBM Transport: Message Fragment P2 Sends per SecondCollects the "Broker/DBM Transport: Message Fragment P2 Sends per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_MessageFragmentP2SendsSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_MessageFragmentP3SendsSecMSSQL on Linux: Broker/DBM Transport: Message Fragment P3 Sends per SecondCollects the "Broker/DBM Transport: Message Fragment P3 Sends per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_MessageFragmentP3SendsSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_MessageFragmentP4SendsSecMSSQL on Linux: Broker/DBM Transport: Message Fragment P4 Sends per SecondCollects the "Broker/DBM Transport: Message Fragment P4 Sends per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_MessageFragmentP4SendsSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_MessageFragmentP5SendsSecMSSQL on Linux: Broker/DBM Transport: Message Fragment P5 Sends per SecondCollects the "Broker/DBM Transport: Message Fragment P5 Sends per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_MessageFragmentP5SendsSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_MessageFragmentP6SendsSecMSSQL on Linux: Broker/DBM Transport: Message Fragment P6 Sends per SecondCollects the "Broker/DBM Transport: Message Fragment P6 Sends per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_MessageFragmentP6SendsSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_MessageFragmentP7SendsSecMSSQL on Linux: Broker/DBM Transport: Message Fragment P7 Sends per SecondCollects the "Broker/DBM Transport: Message Fragment P7 Sends per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_MessageFragmentP7SendsSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_MessageFragmentP8SendsSecMSSQL on Linux: Broker/DBM Transport: Message Fragment P8 Sends per SecondCollects the "Broker/DBM Transport: Message Fragment P8 Sends per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_MessageFragmentP8SendsSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_MessageFragmentP9SendsSecMSSQL on Linux: Broker/DBM Transport: Message Fragment P9 Sends per SecondCollects the "Broker/DBM Transport: Message Fragment P9 Sends per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_MessageFragmentP9SendsSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_MessageFragmentReceivesSecMSSQL on Linux: Broker/DBM Transport: Message Fragment Receives per SecondCollects the "Broker/DBM Transport: Message Fragment Receives per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_MessageFragmentReceivesSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_MessageFragmentSendsSecMSSQL on Linux: Broker/DBM Transport: Message Fragment Sends per SecondCollects the "Broker/DBM Transport: Message Fragment Sends per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_MessageFragmentSendsSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_MsgFragmentRecvSizeAvgMSSQL on Linux: Broker/DBM Transport: Message Fragment Receive Size AverageCollects the "Broker/DBM Transport: Message Fragment Receive Size Average" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_MsgFragmentRecvSizeAvgMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_MsgFragmentSendSizeAvgMSSQL on Linux: Broker/DBM Transport: Message Fragment Send Size AverageCollects the "Broker/DBM Transport: Message Fragment Send Size Average" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_MsgFragmentSendSizeAvgMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_OpenConnectionCountMSSQL on Linux: Broker/DBM Transport: Open Connection CountCollects the "Broker/DBM Transport: Open Connection Count" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_OpenConnectionCountMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_PendingBytesForRecvIOMSSQL on Linux: Broker/DBM Transport: Pending Bytes for Receive I/OCollects the "Broker/DBM Transport: Pending Bytes for Receive I/O" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_PendingBytesForRecvIOMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_PendingBytesForSendIOMSSQL on Linux: Broker/DBM Transport: Pending Bytes for Send I/OCollects the "Broker/DBM Transport: Pending Bytes for Send I/O" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_PendingBytesForSendIOMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_PendingMsgFragsForRecvIOMSSQL on Linux: Broker/DBM Transport: Pending Message Fragments for Receive I/OCollects the "Broker/DBM Transport: Pending Message Fragments for Receive I/O" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_PendingMsgFragsForRecvIOMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_PendingMsgFragsForSendIOMSSQL on Linux: Broker/DBM Transport: Pending Message Fragments for Send I/OCollects the "Broker/DBM Transport: Pending Message Fragments for Send I/O" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_PendingMsgFragsForSendIOMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_ReceiveIOBytesSecMSSQL on Linux: Broker/DBM Transport: Receive I/O Bytes per SecondCollects the "Broker/DBM Transport: Receive I/O Bytes per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_ReceiveIOBytesSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_ReceiveIOLenAvgMSSQL on Linux: Broker/DBM Transport: Receive I/O Len AverageCollects the "Broker/DBM Transport: Receive I/O Len Average" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_ReceiveIOLenAvgMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_ReceiveIOsSecMSSQL on Linux: Broker/DBM Transport: Receive I/Os per SecondCollects the "Broker/DBM Transport: Receive I/Os per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_ReceiveIOsSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_RecvIOBufferCopiesBytesSecMSSQL on Linux: Broker/DBM Transport: Receive I/O Buffer Copies bytes per SecondCollects the "Broker/DBM Transport: Receive I/O Buffer Copies bytes per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_RecvIOBufferCopiesBytesSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_RecvIOBufferCopiesCountMSSQL on Linux: Broker/DBM Transport: Receive I/O Buffer Copies CountCollects the "Broker/DBM Transport: Receive I/O Buffer Copies Count" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_RecvIOBufferCopiesCountMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_SendIOBytesSecMSSQL on Linux: Broker/DBM Transport: Send I/O Bytes per SecondCollects the "Broker/DBM Transport: Send I/O Bytes per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_SendIOBytesSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_SendIOLenAvgMSSQL on Linux: Broker/DBM Transport: Send I/O Len AverageCollects the "Broker/DBM Transport: Send I/O Len Average" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_SendIOLenAvgMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_SendIOsSecMSSQL on Linux: Broker/DBM Transport: Send I/Os per SecondCollects the "Broker/DBM Transport: Send I/Os per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerDbmTransport_SendIOsSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_ActivationErrorsTotalMSSQL on Linux: Broker Statistics: Activation Errors TotalCollects the "Broker Statistics: Activation Errors Total" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_ActivationErrorsTotalMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_BrokerTransactionRollbacksMSSQL on Linux: Broker Statistics: Broker Transaction RollbacksCollects the "Broker Statistics: Broker Transaction Rollbacks" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_BrokerTransactionRollbacksMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_CorruptedMessagesTotalMSSQL on Linux: Broker Statistics: Corrupted Messages TotalCollects the "Broker Statistics: Corrupted Messages Total" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_CorruptedMessagesTotalMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_DequeuedTransmissionqMsgsSecMSSQL on Linux: Broker Statistics: Dequeued TransmissionQ Messages per SecondCollects the "Broker Statistics: Dequeued TransmissionQ Messages per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_DequeuedTransmissionqMsgsSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_DialogTimerEventCountMSSQL on Linux: Broker Statistics: Dialog Timer Event CountCollects the "Broker Statistics: Dialog Timer Event Count" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_DialogTimerEventCountMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_DroppedMessagesTotalMSSQL on Linux: Broker Statistics: Dropped Messages TotalCollects the "Broker Statistics: Dropped Messages Total" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_DroppedMessagesTotalMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedLocalMessagesSecMSSQL on Linux: Broker Statistics: Enqueued Local Messages per SecondCollects the "Broker Statistics: Enqueued Local Messages per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedLocalMessagesSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedLocalMessagesTotalMSSQL on Linux: Broker Statistics: Enqueued Local Messages TotalCollects the "Broker Statistics: Enqueued Local Messages Total" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedLocalMessagesTotalMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedMessagesSecMSSQL on Linux: Broker Statistics: Enqueued Messages per SecondCollects the "Broker Statistics: Enqueued Messages per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedMessagesSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedMessagesTotalMSSQL on Linux: Broker Statistics: Enqueued Messages TotalCollects the "Broker Statistics: Enqueued Messages Total" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedMessagesTotalMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedP10MessagesSecMSSQL on Linux: Broker Statistics: Enqueued P10 Messages per SecondCollects the "Broker Statistics: Enqueued P10 Messages per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedP10MessagesSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedP1MessagesSecMSSQL on Linux: Broker Statistics: Enqueued P1 Messages per SecondCollects the "Broker Statistics: Enqueued P1 Messages per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedP1MessagesSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedP2MessagesSecMSSQL on Linux: Broker Statistics: Enqueued P2 Messages per SecondCollects the "Broker Statistics: Enqueued P2 Messages per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedP2MessagesSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedP3MessagesSecMSSQL on Linux: Broker Statistics: Enqueued P3 Messages per SecondCollects the "Broker Statistics: Enqueued P3 Messages per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedP3MessagesSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedP4MessagesSecMSSQL on Linux: Broker Statistics: Enqueued P4 Messages per SecondCollects the "Broker Statistics: Enqueued P4 Messages per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedP4MessagesSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedP5MessagesSecMSSQL on Linux: Broker Statistics: Enqueued P5 Messages per SecondCollects the "Broker Statistics: Enqueued P5 Messages per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedP5MessagesSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedP6MessagesSecMSSQL on Linux: Broker Statistics: Enqueued P6 Messages per SecondCollects the "Broker Statistics: Enqueued P6 Messages per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedP6MessagesSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedP7MessagesSecMSSQL on Linux: Broker Statistics: Enqueued P7 Messages per SecondCollects the "Broker Statistics: Enqueued P7 Messages per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedP7MessagesSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedP8MessagesSecMSSQL on Linux: Broker Statistics: Enqueued P8 Messages per SecondCollects the "Broker Statistics: Enqueued P8 Messages per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedP8MessagesSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedP9MessagesSecMSSQL on Linux: Broker Statistics: Enqueued P9 Messages per SecondCollects the "Broker Statistics: Enqueued P9 Messages per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedP9MessagesSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedTransmissionqMsgsSecMSSQL on Linux: Broker Statistics: Enqueued TransmissionQ Messages per SecondCollects the "Broker Statistics: Enqueued TransmissionQ Messages per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedTransmissionqMsgsSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedTransportMsgFragsSecMSSQL on Linux: Broker Statistics: Enqueued Transport Message Fragments per SecondCollects the "Broker Statistics: Enqueued Transport Message Fragments per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedTransportMsgFragsSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedTransportMsgFragTotMSSQL on Linux: Broker Statistics: Enqueued Transport Message Frag TotCollects the "Broker Statistics: Enqueued Transport Message Frag Tot" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedTransportMsgFragTotMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedTransportMsgsSecMSSQL on Linux: Broker Statistics: Enqueued Transport Messages per SecondCollects the "Broker Statistics: Enqueued Transport Messages per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedTransportMsgsSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedTransportMsgsTotalMSSQL on Linux: Broker Statistics: Enqueued Transport Messages TotalCollects the "Broker Statistics: Enqueued Transport Messages Total" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_EnqueuedTransportMsgsTotalMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_ForwardedMessagesSecMSSQL on Linux: Broker Statistics: Forwarded Messages per SecondCollects the "Broker Statistics: Forwarded Messages per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_ForwardedMessagesSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_ForwardedMessagesTotalMSSQL on Linux: Broker Statistics: Forwarded Messages TotalCollects the "Broker Statistics: Forwarded Messages Total" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_ForwardedMessagesTotalMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_ForwardedMsgBytesSecMSSQL on Linux: Broker Statistics: Forwarded Message Bytes per SecondCollects the "Broker Statistics: Forwarded Message Bytes per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_ForwardedMsgBytesSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_ForwardedMsgByteTotalMSSQL on Linux: Broker Statistics: Forwarded Message Byte TotalCollects the "Broker Statistics: Forwarded Message Byte Total" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_ForwardedMsgByteTotalMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_ForwardedMsgDiscardedTotalMSSQL on Linux: Broker Statistics: Forwarded Message Discarded TotalCollects the "Broker Statistics: Forwarded Message Discarded Total" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_ForwardedMsgDiscardedTotalMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_ForwardedMsgsDiscardedSecMSSQL on Linux: Broker Statistics: Forwarded Messages Discarded per SecondCollects the "Broker Statistics: Forwarded Messages Discarded per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_ForwardedMsgsDiscardedSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_ForwardedPendingMsgBytesMSSQL on Linux: Broker Statistics: Forwarded Pending Message BytesCollects the "Broker Statistics: Forwarded Pending Message Bytes" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_ForwardedPendingMsgBytesMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_ForwardedPendingMsgCountMSSQL on Linux: Broker Statistics: Forwarded Pending Message CountCollects the "Broker Statistics: Forwarded Pending Message Count" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_ForwardedPendingMsgCountMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_SqlReceivesSecMSSQL on Linux: Broker Statistics: SQL Receives per SecondCollects the "Broker Statistics: SQL Receives per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_SqlReceivesSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_SqlReceiveTotalMSSQL on Linux: Broker Statistics: SQL Receive TotalCollects the "Broker Statistics: SQL Receive Total" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_SqlReceiveTotalMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_SqlSendsSecMSSQL on Linux: Broker Statistics: SQL Sends per SecondCollects the "Broker Statistics: SQL Sends per Second" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_SqlSendsSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_SqlSendTotalMSSQL on Linux: Broker Statistics: SQL Send TotalCollects the "Broker Statistics: SQL Send Total" performance counter for each instance of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BrokerStatistics_SqlSendTotalMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BufferCacheHitRatioMSSQL on Linux: Buffer Cache Hit RatioCollects the Linux "Buffer Cache Hit Ratio" performance counter for each instance of SQL DB Engine on Linux.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.BufferCacheHitRatioMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_AvgBytesReadMSSQL on Linux: HTTP Storage: Average Bytes/ReadCollects the "HTTP Storage: Average Bytes/Read" performance counter for SQL DB Engine that monitor Azure Storage account.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_AvgBytesReadMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_AvgBytesTransferMSSQL on Linux: HTTP Storage: Average Bytes/TransferCollects the "HTTP Storage: Average Bytes/Transfer" performance counter for SQL DB Engine that monitor Azure Storage account.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_AvgBytesTransferMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_AvgBytesWriteMSSQL on Linux: HTTP Storage: Average Bytes/WriteCollects the "HTTP Storage: Average Bytes/Write" performance counter for SQL DB Engine that monitor Azure Storage account.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_AvgBytesWriteMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_AvgMicrosecReadMSSQL on Linux: HTTP Storage: Average Microseconds/ReadCollects the "HTTP Storage: Average Microseconds/Read" performance counter for SQL DB Engine that monitor Azure Storage account.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_AvgMicrosecReadMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_AvgMicrosecReadCompMSSQL on Linux: HTTP Storage: Average Microseconds/Read CompCollects the "HTTP Storage: Average Microseconds/Read Comp" performance counter for SQL DB Engine that monitor Azure Storage account.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_AvgMicrosecReadCompMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_AvgMicrosecTransferMSSQL on Linux: HTTP Storage: Average Microseconds/TransferCollects the "HTTP Storage: Average Microseconds/Transfer" performance counter for SQL DB Engine that monitor Azure Storage account.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_AvgMicrosecTransferMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_AvgMicrosecWriteMSSQL on Linux: HTTP Storage: Average Microseconds/WriteCollects the "HTTP Storage: Average Microseconds/Write" performance counter for SQL DB Engine that monitor Azure Storage account.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_AvgMicrosecWriteMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_AvgMicrosecWriteCompMSSQL on Linux: HTTP Storage: Average Microseconds/Write CompCollects the "HTTP Storage: Average Microseconds/Write Comp" performance counter for SQL DB Engine that monitor Azure Storage account.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_AvgMicrosecWriteCompMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_HttpStorageIoFailedSecMSSQL on Linux: HTTP Storage: HTTP Storage I/O Failed per SecondCollects the "HTTP Storage: HTTP Storage I/O Failed per Second" performance counter for SQL DB Engine that monitor c.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_HttpStorageIoFailedSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_HttpStorageIoRetrySecMSSQL on Linux: HTTP Storage: HTTP Storage I/O Retry per SecondCollects the "HTTP Storage: HTTP Storage I/O Retry per Second" performance counter for SQL DB Engine that monitor Azure Storage account.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_HttpStorageIoRetrySecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_OutstandingHttpStorageIoMSSQL on Linux: HTTP Storage: Outstanding HTTP Storage I/OCollects the "HTTP Storage: Outstanding HTTP Storage I/O" performance counter for SQL DB Engine that monitor Azure Storage account.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_OutstandingHttpStorageIoMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_ReadBytesSecMSSQL on Linux: HTTP Storage: Read Bytes per SecondCollects the "HTTP Storage: Read Bytes per Second" performance counter for SQL DB Engine that monitor Azure Storage account.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_ReadBytesSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_ReadsSecMSSQL on Linux: HTTP Storage: Reads per SecondCollects the "HTTP Storage: Reads per Second" performance counter for SQL DB Engine that monitor Azure Storage account.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_ReadsSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_TotalBytesSecMSSQL on Linux: HTTP Storage: Total Bytes per SecondCollects the "HTTP Storage: Total Bytes per Second" performance counter for SQL DB Engine that monitor Azure Storage account.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_TotalBytesSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_TransfersSecMSSQL on Linux: HTTP Storage: Transfers per SecondCollects the "HTTP Storage: Transfers per Second" performance counter for SQL DB Engine that monitor Azure Storage account.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_TransfersSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_WriteBytesSecMSSQL on Linux: HTTP Storage: Write Bytes per SecondCollects the "HTTP Storage: Write Bytes per Second" performance counter for SQL DB Engine that monitor Azure Storage account.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_WriteBytesSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_WritesSecMSSQL on Linux: HTTP Storage: Writes per SecondCollects the "HTTP Storage: Writes per Second" performance counter for SQL DB Engine that monitor Azure Storage account.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.HTTPStorage_WritesSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.LockRequestsPerSecondMSSQL on Linux: Number of Lock Requests per SecondCollects the Linux "Number of Lock Requests per Second" performance counter for each instance of SQL DB Engine on Linux.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.LockRequestsPerSecondMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.LockTimeoutsPerSecondMSSQL on Linux: Lock Timeouts per SecondCollects the Linux "Lock Timeouts per Second" performance counter for each instance of SQL DB Engine on Linux.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.LockTimeoutsPerSecondMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.LockWaitsPerSecondMSSQL on Linux: Number of Lock Waits per SecondCollects the Linux "Number of Lock Waits per Second" performance counter for each instance of SQL DB Engine on Linux.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.LockWaitsPerSecondMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.LoginsPerSecondMSSQL on Linux: Logins per SecondTotal number of logins started per second. This does not include pooled connections.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.LoginsPerSecondMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.NumberDeadlocksPerSecondMSSQL on Linux: Number of Deadlocks per SecondCollects the Linux "Number of Deadlocks per Second" performance counter for each instance of SQL DB Engine on Linux.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.NumberDeadlocksPerSecondMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.PageLifeExpectancyMSSQL on Linux: DB Engine Page Life Expectancy (s)SQL DB Engine on Linux Page Life Expectancy (s) performance collection ruleMicrosoft.SQLServer.Linux.CollectionRule.DBEngine.PageLifeExpectancyMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.SQLCompilationsPerSecondMSSQL on Linux: SQL Compilations per SecondCollects the Linux "SQL Compilations per Second" performance counter for each instance of SQL DB Engine on Linux.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.SQLCompilationsPerSecondMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.SQLRecompilationsPerSecondMSSQL on Linux: SQL Re-Compilations per SecondCollects the Linux "SQL Recompiles per Second" performance counter for each instance of SQL DB Engine on Linux.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.SQLRecompilationsPerSecondMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.StolenServerMemoryMSSQL on Linux: DB Engine Stolen Server Memory (MB)SQL DB Engine Stolen Server Memory (MB) performance collection rule on LinuxMicrosoft.SQLServer.Linux.CollectionRule.DBEngine.StolenServerMemoryMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.ThreadCountMSSQL on Linux: DB Engine Thread CountSQL DB Engine Thread Count performance collection ruleMicrosoft.SQLServer.Linux.CollectionRule.DBEngine.ThreadCountMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.TransactionsPerSecondMSSQL on Linux: Total Transactions per SecondCollects the Linux "Transaction per Second" performance counter for the _Total instance of the databases performance object for each instance of SQL DB Engine on Linux.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.TransactionsPerSecondMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.UserConnectionsCollectionMSSQL on Linux: SQL User ConnectionsCounts the number of users currently connected to SQL Server.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.UserConnectionsCollectionMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpCursors_CursorDeletesSecMSSQL on Linux: Cursor deletes/secCollects the Linux "Cursor deletes/sec" performance counter for internal XTP engine cursors.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpCursors_CursorDeletesSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpCursors_CursorInsertsSecMSSQL on Linux: Cursor inserts/secCollects the Linux "Cursor inserts/sec" performance counter for internal XTP engine cursors.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpCursors_CursorInsertsSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpCursors_CursorScansStartedSecMSSQL on Linux: Cursor scans started/secCollects the Linux "Cursor scans started/sec" performance counter for internal XTP engine cursors.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpCursors_CursorScansStartedSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpCursors_CursorUniqueViolationsSecMSSQL on Linux: Cursor unique violations/secCollects the Linux "Cursor unique violations/sec" performance counter for internal XTP engine cursors.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpCursors_CursorUniqueViolationsSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpCursors_CursorUpdatesSecMSSQL on Linux: Cursor updates/secCollects the Linux "Cursor updates/sec" performance counter for internal XTP engine cursors.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpCursors_CursorUpdatesSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpCursors_CursorWriteConflictsSecMSSQL on Linux: Cursor write conflicts/secCollects the Linux "Cursor write conflicts/sec" performance counter for internal XTP engine cursors.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpCursors_CursorWriteConflictsSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpCursors_DustyCornerScanRetriesSecUserIssuedMSSQL on Linux: Dusty corner scan retries/sec (user-issued)Collects the Linux "Dusty corner scan retries/sec (user-issued)" performance counter for internal XTP engine cursors.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpCursors_DustyCornerScanRetriesSecUserIssuedMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpCursors_ExpiredRowsRemovedSecMSSQL on Linux: Expired rows removed/secCollects the Linux "Expired rows removed/sec" performance counter for internal XTP engine cursors.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpCursors_ExpiredRowsRemovedSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpCursors_ExpiredRowsTouchedSecMSSQL on Linux: Expired rows touched/secCollects the Linux "Expired rows touched/sec" performance counter for internal XTP engine cursors.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpCursors_ExpiredRowsTouchedSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpCursors_RowsReturnedSecMSSQL on Linux: Rows returned/secCollects the Linux "Rows returned/sec" performance counter for internal XTP engine cursors.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpCursors_RowsReturnedSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpCursors_RowsTouchedSecMSSQL on Linux: Rows touched/secCollects the Linux "Rows touched/sec" performance counter for internal XTP engine cursors.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpCursors_RowsTouchedSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpCursors_TentativelyDeletedRowsTouchedSecMSSQL on Linux: Tentatively-deleted rows touched/secCollects the Linux "Tentatively-deleted rows touched/sec" performance counter for internal XTP engine cursors.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpCursors_TentativelyDeletedRowsTouchedSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpGarbageCollection_DustyCornerScanRetriesSecGcIssuedMSSQL on Linux: Dusty corner scan retries/sec (GC-issued)Collects the Linux "Dusty corner scan retries/sec (GC-issued)" performance counter for the XTP engine's garbage collector.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpGarbageCollection_DustyCornerScanRetriesSecGcIssuedMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpGarbageCollection_MainGcWorkItemsSecMSSQL on Linux: Main GC work items/secCollects the Linux "Main GC work items/sec" performance counter for the XTP engine's garbage collector.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpGarbageCollection_MainGcWorkItemsSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpGarbageCollection_ParallelGcWorkItemSecMSSQL on Linux: Parallel GC work item/secCollects the Linux "Parallel GC work item/sec" performance counter for the XTP engine's garbage collector.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpGarbageCollection_ParallelGcWorkItemSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpGarbageCollection_RowsProcessedSecMSSQL on Linux: Rows processed/secCollects the Linux "Rows processed/sec" performance counter for the XTP engine's garbage collector.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpGarbageCollection_RowsProcessedSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpGarbageCollection_RowsProcessedSecFirstInBucketMSSQL on Linux: Rows processed/sec (first in bucket)Collects the Linux "Rows processed/sec (first in bucket)" performance counter for the XTP engine's garbage collector.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpGarbageCollection_RowsProcessedSecFirstInBucketMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpGarbageCollection_RowsProcessedSecFirstInBucketAndRemovedMSSQL on Linux: Rows processed/sec (first in bucket and removed)Collects the Linux "Rows processed/sec (first in bucket and removed)" performance counter for the XTP engine's garbage collector.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpGarbageCollection_RowsProcessedSecFirstInBucketAndRemovedMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpGarbageCollection_RowsProcessedSecMarkedForUnlinkMSSQL on Linux: Rows processed/sec (marked for unlink)Collects the Linux "Rows processed/sec (marked for unlink)" performance counter for the XTP engine's garbage collector.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpGarbageCollection_RowsProcessedSecMarkedForUnlinkMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpGarbageCollection_RowsProcessedSecNoSweepNeededMSSQL on Linux: Rows processed/sec (no sweep needed)Collects the Linux "Rows processed/sec (no sweep needed)" performance counter for the XTP engine's garbage collector.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpGarbageCollection_RowsProcessedSecNoSweepNeededMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpGarbageCollection_SweepExpiredRowsRemovedSecMSSQL on Linux: Sweep expired rows removed/secCollects the Linux "Sweep expired rows removed/sec" performance counter for the XTP engine's garbage collector.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpGarbageCollection_SweepExpiredRowsRemovedSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpGarbageCollection_SweepExpiredRowsTouchedSecMSSQL on Linux: Sweep expired rows touched/secCollects the Linux "Sweep expired rows touched/sec" performance counter for the XTP engine's garbage collector.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpGarbageCollection_SweepExpiredRowsTouchedSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpGarbageCollection_SweepExpiringRowsTouchedSecMSSQL on Linux: Sweep expiring rows touched/secCollects the Linux "Sweep expiring rows touched/sec" performance counter for the XTP engine's garbage collector.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpGarbageCollection_SweepExpiringRowsTouchedSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpGarbageCollection_SweepRowsTouchedSecMSSQL on Linux: Sweep rows touched/secCollects the Linux "Sweep rows touched/sec" performance counter for the XTP engine's garbage collector.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpGarbageCollection_SweepRowsTouchedSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpGarbageCollection_SweepScansStartedSecMSSQL on Linux: Sweep scans started/secCollects the Linux "Sweep scans started/sec" performance counter for the XTP engine's garbage collector.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpGarbageCollection_SweepScansStartedSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpIoGovernor_InsufficientCreditsWaitsSecMSSQL on Linux: Insufficient Credits Waits/secCollects the Linux "Insufficient Credits Waits/sec" performance counter for the XTP IO Rate Governor.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpIoGovernor_InsufficientCreditsWaitsSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpIoGovernor_IoIssuedSecMSSQL on Linux: Io Issued/secCollects the Linux "Io Issued/sec" performance counter for the XTP IO Rate Governor.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpIoGovernor_IoIssuedSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpIoGovernor_LogBlocksSecMSSQL on Linux: Log Blocks/secCollects the Linux "Log Blocks/sec" performance counter for the XTP IO Rate Governor.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpIoGovernor_LogBlocksSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpIoGovernor_MissedCreditSlotsMSSQL on Linux: Missed Credit SlotsCollects the Linux "Missed Credit Slots" performance counter for the XTP IO Rate Governor.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpIoGovernor_MissedCreditSlotsMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpIoGovernor_StaleRateObjectWaitsSecMSSQL on Linux: Stale Rate Object Waits/secCollects the Linux "Stale Rate Object Waits/sec" performance counter for the XTP IO Rate Governor.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpIoGovernor_StaleRateObjectWaitsSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpIoGovernor_TotalRateObjectsPublishedMSSQL on Linux: Total Rate Objects PublishedCollects the Linux "Total Rate Objects Published" performance counter for the XTP IO Rate Governor.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpIoGovernor_TotalRateObjectsPublishedMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpPhantomProcessor_DustyCornerScanRetriesSecPhantomIssuedMSSQL on Linux: Dusty corner scan retries/sec (Phantom-issued)Collects the Linux "Dusty corner scan retries/sec (Phantom-issued)" performance counter for the XTP engine's phantom processing subsystem.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpPhantomProcessor_DustyCornerScanRetriesSecPhantomIssuedMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpPhantomProcessor_PhantomExpiredRowsRemovedSecMSSQL on Linux: Phantom expired rows removed/secCollects the Linux "Phantom expired rows removed/sec" performance counter for the XTP engine's phantom processing subsystem.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpPhantomProcessor_PhantomExpiredRowsRemovedSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpPhantomProcessor_PhantomExpiredRowsTouchedSecMSSQL on Linux: Phantom expired rows touched/secCollects the Linux "Phantom expired rows touched/sec" performance counter for the XTP engine's phantom processing subsystem.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpPhantomProcessor_PhantomExpiredRowsTouchedSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpPhantomProcessor_PhantomExpiringRowsTouchedSecMSSQL on Linux: Phantom expiring rows touched/secCollects the Linux "Phantom expiring rows touched/sec" performance counter for the XTP engine's phantom processing subsystem.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpPhantomProcessor_PhantomExpiringRowsTouchedSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpPhantomProcessor_PhantomRowsTouchedSecMSSQL on Linux: Phantom rows touched/secCollects the Linux "Phantom rows touched/sec" performance counter for the XTP engine's phantom processing subsystem.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpPhantomProcessor_PhantomRowsTouchedSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpPhantomProcessor_PhantomScansStartedSecMSSQL on Linux: Phantom scans started/secCollects the Linux "Phantom scans started/sec" performance counter for the XTP engine's phantom processing subsystem.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpPhantomProcessor_PhantomScansStartedSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpStorage_CheckpointsClosedMSSQL on Linux: Checkpoints ClosedCollects the Linux "Checkpoints Closed" performance counter for the XTP engine's storage subsystem.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpStorage_CheckpointsClosedMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpStorage_CheckpointsCompletedMSSQL on Linux: Checkpoints CompletedCollects the Linux "Checkpoints Completed" performance counter for the XTP engine's storage subsystem.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpStorage_CheckpointsCompletedMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpStorage_CoreMergesCompletedMSSQL on Linux: Core Merges CompletedCollects the Linux "Core Merges Completed" performance counter for the XTP engine's storage subsystem.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpStorage_CoreMergesCompletedMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpStorage_MergePolicyEvaluationsMSSQL on Linux: Merge Policy EvaluationsCollects the Linux "Merge Policy Evaluations" performance counter for the XTP engine's storage subsystem.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpStorage_MergePolicyEvaluationsMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpStorage_MergeRequestsOutstandingMSSQL on Linux: Merge Requests OutstandingCollects the Linux "Merge Requests Outstanding" performance counter for the XTP engine's storage subsystem.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpStorage_MergeRequestsOutstandingMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpStorage_MergesAbandonedMSSQL on Linux: Merges AbandonedCollects the Linux "Merges Abandoned" performance counter for the XTP engine's storage subsystem.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpStorage_MergesAbandonedMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpStorage_MergesInstalledMSSQL on Linux: Merges InstalledCollects the Linux "Merges Installed" performance counter for the XTP engine's storage subsystem.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpStorage_MergesInstalledMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpStorage_TotalFilesMergedMSSQL on Linux: Total Files MergedCollects the Linux "Total Files Merged" performance counter for the XTP engine's storage subsystem.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpStorage_TotalFilesMergedMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpTransactionLog_LogBytesWrittenSecMSSQL on Linux: Log bytes written/secCollects the Linux "Log bytes written/sec" performance counter for XTP transaction logging in SQL Server.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpTransactionLog_LogBytesWrittenSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpTransactionLog_LogRecordsWrittenSecMSSQL on Linux: Log records written/secCollects the Linux "Log records written/sec" performance counter for XTP transaction logging in SQL Server.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpTransactionLog_LogRecordsWrittenSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpTransactions_CascadingAbortsSecMSSQL on Linux: Cascading aborts/secCollects the Linux "Cascading aborts/sec" performance counter for XTP engine transactions in SQL Server.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpTransactions_CascadingAbortsSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpTransactions_CommitDependenciesTakenSecMSSQL on Linux: Commit dependencies taken/secCollects the Linux "Commit dependencies taken/sec" performance counter for XTP engine transactions in SQL Server.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpTransactions_CommitDependenciesTakenSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpTransactions_ReadOnlyTransactionsPreparedSecMSSQL on Linux: Read-only transactions prepared/secCollects the Linux "Read-only transactions prepared/sec" performance counter for XTP engine transactions in SQL Server.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpTransactions_ReadOnlyTransactionsPreparedSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpTransactions_SavePointRefreshesSecMSSQL on Linux: Save point refreshes/secCollects the Linux "Save point refreshes/sec" performance counter for XTP engine transactions in SQL Server.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpTransactions_SavePointRefreshesSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpTransactions_SavePointRollbacksSecMSSQL on Linux: Save point rollbacks/secCollects the Linux "Save point rollbacks/sec" performance counter for XTP engine transactions in SQL Server.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpTransactions_SavePointRollbacksSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpTransactions_SavePointsCreatedSecMSSQL on Linux: Save points created/secCollects the Linux "Save points created/sec" performance counter for XTP engine transactions in SQL Server.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpTransactions_SavePointsCreatedSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpTransactions_TransactionsAbortedByUserSecMSSQL on Linux: Transactions aborted by user/secCollects the Linux "Transactions aborted by user/sec" performance counter for XTP engine transactions in SQL Server.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpTransactions_TransactionsAbortedByUserSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpTransactions_TransactionsAbortedSecMSSQL on Linux: Transactions aborted/secCollects the Linux "Transactions aborted/sec" performance counter for XTP engine transactions in SQL Server.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpTransactions_TransactionsAbortedSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpTransactions_TransactionsCreatedSecMSSQL on Linux: Transactions created/secCollects the Linux "Transactions created/sec" performance counter for XTP engine transactions in SQL Server.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpTransactions_TransactionsCreatedSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpTransactions_TransactionValidationFailuresSecMSSQL on Linux: Transaction validation failures/secCollects the Linux "Transaction validation failures/sec" performance counter for XTP engine transactions in SQL Server.Microsoft.SQLServer.Linux.CollectionRule.DBEngine.XtpTransactions_TransactionValidationFailuresSecMicrosoft.SQLServer.Linux.DBEnginePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBFile.FileAllocatedSpaceLeftMBMSSQL on Linux: 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.Linux.CollectionRule.DBFile.FileAllocatedSpaceLeftMBMicrosoft.SQLServer.Linux.DBFilePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBFile.FileAllocatedSpaceLeftPercentMSSQL on Linux: 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 enabledMicrosoft.SQLServer.Linux.CollectionRule.DBFile.FileAllocatedSpaceLeftPercentMicrosoft.SQLServer.Linux.DBFilePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBFile.SpaceFreeMegabytesMSSQL on Linux: 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.Linux.CollectionRule.DBFile.SpaceFreeMegabytesMicrosoft.SQLServer.Linux.DBFilePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBFile.SpaceFreePercentMSSQL on Linux: 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.Linux.CollectionRule.DBFile.SpaceFreePercentMicrosoft.SQLServer.Linux.DBFilePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBFileGroupFx.CheckpointFile.ActiveMSSQL on Linux: Active Checkpoint File PairsCollects the number of active checkpoint file pairs in Memory-Optimized Data Filegroup.Microsoft.SQLServer.Linux.CollectionRule.DBFileGroupFx.CheckpointFile.ActiveMicrosoft.SQLServer.Linux.DBFilegroupFxPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBFileGroupFx.CheckpointFile.MergeTargetMSSQL on Linux: Merge Target Checkpoint File PairsCollects the number of merge target checkpoint file pairs in Memory-Optimized Data Filegroup.Microsoft.SQLServer.Linux.CollectionRule.DBFileGroupFx.CheckpointFile.MergeTargetMicrosoft.SQLServer.Linux.DBFilegroupFxPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBFileGroupFx.CheckpointFile.PrecreatedMSSQL on Linux: Precreated Checkpoint FilesCollects the number of Precreated Checkpoint Files in Memory-Optimized Data Filegroup.Microsoft.SQLServer.Linux.CollectionRule.DBFileGroupFx.CheckpointFile.PrecreatedMicrosoft.SQLServer.Linux.DBFilegroupFxPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBFileGroupFx.CheckpointFile.StaleMSSQL on Linux: Checkpoint File Pairs Waiting For Log TruncationCollects the number of Checkpoint Files Waiting For Log Truncation in Memory-Optimized Data Filegroup.Microsoft.SQLServer.Linux.CollectionRule.DBFileGroupFx.CheckpointFile.StaleMicrosoft.SQLServer.Linux.DBFilegroupFxPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBFileGroupFx.CheckpointFile.UnderConstructionMSSQL on Linux: Checkpoint File Pairs Under ConstructionCollects the number of checkpoint file pairs under construction in Memory-Optimized Data Filegroup.Microsoft.SQLServer.Linux.CollectionRule.DBFileGroupFx.CheckpointFile.UnderConstructionMicrosoft.SQLServer.Linux.DBFilegroupFxPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBFilegroupFx.IndexesUsedMemoryMBMSSQL on Linux: Memory Used By Indexes (MB)Collects the amount of memory allocated for indexes defined for memory-optimized tables in the given SQL Server Database on Linux.Microsoft.SQLServer.Linux.CollectionRule.DBFilegroupFx.IndexesUsedMemoryMBMicrosoft.SQLServer.Linux.DBFilegroupFxPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBFilegroupFx.TablesMemoryUsageMBMSSQL on Linux: Memory Used By Tables (MB)Collects the amount of memory allocated for memory-optimized tables in the given SQL Server Database on Linux.Microsoft.SQLServer.Linux.CollectionRule.DBFilegroupFx.TablesMemoryUsageMBMicrosoft.SQLServer.Linux.DBFilegroupFxPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBFilegroupFx.XtpControllerDlcLatencyFetchMSSQL on Linux: XTP Controller DLC Latency/FetchCollects the Linux "XTP Controller DLC Latency/Fetch" performance counter for SQL Database with Memory-Optimized tables.Microsoft.SQLServer.Linux.CollectionRule.DBFilegroupFx.XtpControllerDlcLatencyFetchMicrosoft.SQLServer.Linux.DBFilegroupFxPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBFilegroupFx.XtpControllerDlcPeakLatencyMSSQL on Linux: XTP Controller DLC Peak LatencyCollects the Linux "XTP Controller DLC Peak Latency" performance counter for SQL Database with Memory-Optimized tables.Microsoft.SQLServer.Linux.CollectionRule.DBFilegroupFx.XtpControllerDlcPeakLatencyMicrosoft.SQLServer.Linux.DBFilegroupFxPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBFilegroupFx.XtpControllerLogProcessedSecMSSQL on Linux: XTP Controller Log Processed/secCollects the Linux "XTP Controller Log Processed/sec" performance counter for SQL Database with Memory-Optimized tables.Microsoft.SQLServer.Linux.CollectionRule.DBFilegroupFx.XtpControllerLogProcessedSecMicrosoft.SQLServer.Linux.DBFilegroupFxPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBFilegroupFx.XtpMemoryUsedKbMSSQL on Linux: XTP Memory Used (KB)Collects the Linux "XTP Memory Used (KB)" performance counter for SQL Database with Memory-Optimized tables.Microsoft.SQLServer.Linux.CollectionRule.DBFilegroupFx.XtpMemoryUsedKbMicrosoft.SQLServer.Linux.DBFilegroupFxPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBLogFile.FileAllocatedSpaceLeftMBMSSQL on Linux: 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.Linux.CollectionRule.DBLogFile.FileAllocatedSpaceLeftMBMicrosoft.SQLServer.Linux.DBLogFilePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBLogFile.FileAllocatedSpaceLeftPercentMSSQL on Linux: 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.Linux.CollectionRule.DBLogFile.FileAllocatedSpaceLeftPercentMicrosoft.SQLServer.Linux.DBLogFilePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBLogFile.SpaceFreeMegabytesMSSQL on Linux: 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.Linux.CollectionRule.DBLogFile.SpaceFreeMegabytesMicrosoft.SQLServer.Linux.DBLogFilePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.DBLogFile.SpaceFreePercentMSSQL on Linux: 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.Linux.CollectionRule.DBLogFile.SpaceFreePercentMicrosoft.SQLServer.Linux.DBLogFilePerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.ResourcePool.ActiveMemoryGrantAmountKBMSSQL on Linux: Number of query memory grants in the resource poolCollects the Linux "Active Memory grant amount (KB)" performance counter for each resource pool of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.ResourcePool.ActiveMemoryGrantAmountKBMicrosoft.SQLServer.Linux.ResourcePoolPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.ResourcePool.ActiveMemoryGrantsCountMSSQL on Linux: Total amount of granted memory in the resource pool (KB)Collects the Linux "Active memory grants count" performance counter for each resource pool of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.ResourcePool.ActiveMemoryGrantsCountMicrosoft.SQLServer.Linux.ResourcePoolPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.ResourcePool.CacheMemoryTargetKBMSSQL on Linux: Current memory target for cache memory (KB)Collects the Linux "Cache memory target (KB)" performance counter for each resource pool of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.ResourcePool.CacheMemoryTargetKBMicrosoft.SQLServer.Linux.ResourcePoolPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.ResourcePool.CompileMemoryTargetKBMSSQL on Linux: Current memory target for query compile (KB)Collects the Linux "Compile Memory Target (KB)" performance counter for each resource pool of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.ResourcePool.CompileMemoryTargetKBMicrosoft.SQLServer.Linux.ResourcePoolPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.ResourcePool.MaxMemoryKBMSSQL on Linux: Maximum amount of memory the resource pool can have based on the settings and server state (KB)Collects the Linux "Max memory (KB)" performance counter for each resource pool of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.ResourcePool.MaxMemoryKBMicrosoft.SQLServer.Linux.ResourcePoolPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.ResourcePool.MemoryGrantsSecMSSQL on Linux: Number of query memory grants per second occurring in the resource poolCollects the Linux "Memory grants/sec" performance counter for each resource pool of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.ResourcePool.MemoryGrantsSecMicrosoft.SQLServer.Linux.ResourcePoolPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.ResourcePool.MemoryGrantTimeoutsSecMSSQL on Linux: Number of query memory grant timeouts per second occurring in the resource poolCollects the Linux "Memory grant timeouts/sec" performance counter for each resource pool of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.ResourcePool.MemoryGrantTimeoutsSecMicrosoft.SQLServer.Linux.ResourcePoolPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.ResourcePool.PendingMemoryGrantsCountMSSQL on Linux: Number of queries waiting for memory grants in the resource pool.Collects the Linux "Pending memory grants count" performance counter for each resource pool of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.ResourcePool.PendingMemoryGrantsCountMicrosoft.SQLServer.Linux.ResourcePoolPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.ResourcePool.QueryExecMemoryTargetKBMSSQL on Linux: Current memory target for query execution memory grant (KB)Collects the Linux "Query exec memory target (KB)" performance counter for each resource pool of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.ResourcePool.QueryExecMemoryTargetKBMicrosoft.SQLServer.Linux.ResourcePoolPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.ResourcePool.TargetMemoryKBMSSQL on Linux: Target amount of memory the resource pool is trying to attain based on the settings and server state (KB)Collects the Linux "Target memory (KB)" performance counter for each resource pool of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.ResourcePool.TargetMemoryKBMicrosoft.SQLServer.Linux.ResourcePoolPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.ResourcePool.UsedMemoryKBMSSQL on Linux: Used amount of memory in the resource pool (KB)Collects the Linux "Used memory (KB)" performance counter for each resource pool of SQL DB Engine.Microsoft.SQLServer.Linux.CollectionRule.ResourcePool.UsedMemoryKBMicrosoft.SQLServer.Linux.ResourcePoolPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.UserResourcePool.MemoryConsumptionMBMSSQL on Linux: User Resource Pool Memory Consumption (MB)Collects amount of memory used by the resource pool (in Megabytes).Microsoft.SQLServer.Linux.CollectionRule.UserResourcePool.MemoryConsumptionMBMicrosoft.SQLServer.Linux.UserResourcePoolPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.CollectionRule.UserResourcePool.MemoryConsumptionPercentMSSQL on Linux: 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.Linux.CollectionRule.UserResourcePool.MemoryConsumptionPercentMicrosoft.SQLServer.Linux.UserResourcePoolPerformanceCollectionTrue00FalseTrue
Microsoft.SQLServer.Linux.EventRule.AvailabilityReplica.AvailabilityGroupFailedMSSQL on Linux: Availability Group FailedThis error occurs when an attempt to join the availability replica to the availability group has failed. Note: this rule is disabled by default. Please use overrides to enable it when necessary.Microsoft.SQLServer.Linux.EventRule.AvailabilityReplica.AvailabilityGroupFailedMicrosoft.SQLServer.Linux.AvailabilityReplicaEventCollectionFalse00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.AvailabilityReplica.RoleChangedMSSQL on Windows Always On: Availability Replica Role ChangedThis error occurs when Availability replica changes its role.Microsoft.SQLServer.Linux.EventRule.AvailabilityReplica.RoleChangedMicrosoft.SQLServer.Linux.AvailabilityReplicaEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DatabaseReplica.RoleChangedMSSQL on Linux: Database Replica Role ChangedThis error occurs when Database replica changes its role.Microsoft.SQLServer.Linux.EventRule.DatabaseReplica.RoleChangedMicrosoft.SQLServer.Linux.DatabaseReplicaEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.An_error_occurred_in_a_SQL_Server_Service_Broker_Database_Mirroring_transport_connection_endpoint_1_5_RuleMSSQL on Linux: An error occurred in a SQL Server Service Broker/Database Mirroring transport connection endpointSQL Server uses Service Broker and Database Mirroring endpoints for communication outside of the SQL Server instance.Microsoft.SQLServer.Linux.EventRule.DBEngine.An_error_occurred_in_a_SQL_Server_Service_Broker_Database_Mirroring_transport_connection_endpoint_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.An_error_occurred_in_the_Service_Broker_manager_5_RuleMSSQL on Linux: An error occurred in the Service Broker managerThe rule triggers an alert when an error occurred in the SQL Server Service Broker manager.Microsoft.SQLServer.Linux.EventRule.DBEngine.An_error_occurred_in_the_Service_Broker_manager_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.An_error_occurred_in_the_Service_Broker_queue_rollback_handler_5_RuleMSSQL on Linux: An error occurred in the Service Broker queue rollback handlerSQL Server Service Broker raises MSSQLSERVER event ID 8405 when an error prevents Service Broker from disabling a queue during a rollback.Microsoft.SQLServer.Linux.EventRule.DBEngine.An_error_occurred_in_the_Service_Broker_queue_rollback_handler_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.An_error_occurred_in_the_SQL_Server_Service_Broker_message_dispatcher_5_RuleMSSQL on Linux: An error occurred in the SQL Server Service Broker message dispatcherAn error occurred in the SQL Server Service Broker message dispatcher. The Linux application log or SQL Server error log may identify the specific error.Microsoft.SQLServer.Linux.EventRule.DBEngine.An_error_occurred_in_the_SQL_Server_Service_Broker_message_dispatcher_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.An_error_occurred_in_the_SQL_Server_Service_Broker_message_transmitter_5_RuleMSSQL on Linux: An error occurred in the SQL Server Service Broker message transmitterSQL Server Service Broker message transmitter detected an error.Microsoft.SQLServer.Linux.EventRule.DBEngine.An_error_occurred_in_the_SQL_Server_Service_Broker_message_transmitter_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.An_error_occurred_in_the_SQL_Server_Service_Broker_or_Database_Mirroring_transport_manager_5_RuleMSSQL on Linux: An error occurred in the SQL Server Service Broker or Database Mirroring transport managerAn error occurred in the SQL Server Service Broker or Database Mirroring transport manager. The Linux application log or SQL Server error log may identify the specific error.Microsoft.SQLServer.Linux.EventRule.DBEngine.An_error_occurred_in_the_SQL_Server_Service_Broker_or_Database_Mirroring_transport_manager_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.An_error_occurred_in_the_timer_event_cache_5_RuleMSSQL on Linux: An error occurred in the timer event cacheAn error occurred in the SQL Server Service Broker transport layer timer event cache. The Linux application log or SQL Server error log may identify the specific error.Microsoft.SQLServer.Linux.EventRule.DBEngine.An_error_occurred_in_the_timer_event_cache_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.An_error_occurred_while_processing_SQL_Server_Service_Broker_mirroring_routes_5_RuleMSSQL on Linux: An error occurred while processing SQL Server Service Broker mirroring routesThe rule triggers an alert when an error occurres while processing SQL Server Service Broker mirroring routesMicrosoft.SQLServer.Linux.EventRule.DBEngine.An_error_occurred_while_processing_SQL_Server_Service_Broker_mirroring_routes_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.An_error_occurred_while_processing_the_log_for_database_5_RuleMSSQL on Linux: An error occurred while reading the log for databaseThis error indicates a failure while processing the transaction log during rollback, recovery, or replication.Microsoft.SQLServer.Linux.EventRule.DBEngine.An_error_occurred_while_processing_the_log_for_database_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorHighTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.An_SNI_call_failed_during_a_Service_Broker_Database_Mirroring_transport_operation_1_5_RuleMSSQL on Linux: A SNI call failed during a Service Broker/Database Mirroring transport operationThe rule triggers an alert when a SNI call fails 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.Linux.EventRule.DBEngine.An_SNI_call_failed_during_a_Service_Broker_Database_Mirroring_transport_operation_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionFalse00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.An_SQL_Server_Service_Broker_dialog_caught_an_error_5_RuleMSSQL on Linux: An SQL Server Service Broker dialog detected an errorThe rule triggers an alert when a SQL Server Service Broker dialog detects an errorMicrosoft.SQLServer.Linux.EventRule.DBEngine.An_SQL_Server_Service_Broker_dialog_caught_an_error_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.AppDomain_failed_to_unload_with_error_code_5_RuleMSSQL on Linux: AppDomain failed to unload with error codeThe rule triggers an application domain fails to unload because of some error. The Linux application log may contain an information about the original error code and other diagnostic detailsMicrosoft.SQLServer.Linux.EventRule.DBEngine.AppDomain_failed_to_unload_with_error_code_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Attempt_to_fetch_logical_page_that_belongs_to_different_object_5_RuleMSSQL on Linux: Attempt to fetch logical page that belongs to different objectThis 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.Linux.EventRule.DBEngine.Attempt_to_fetch_logical_page_that_belongs_to_different_object_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorHighTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.A_default_full_text_catalog_does_not_exist_in_the_database_or_user_does_not_have_permission_to_perform_this_action_5_RuleMSSQL on Linux: A default full-text catalog does not exist in the database or user does not have permission to perform this actionThe 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.Linux.EventRule.DBEngine.A_default_full_text_catalog_does_not_exist_in_the_database_or_user_does_not_have_permission_to_perform_this_action_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.A_fatal_error_occurred_in_.NET_Framework_runtime_5_RuleMSSQL on Linux: A fatal error occurred in .NET Framework runtimeThe rule triggers an alert when the .NET Framework shuts down due to an error.Microsoft.SQLServer.Linux.EventRule.DBEngine.A_fatal_error_occurred_in_.NET_Framework_runtime_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.A_security__SSPI__error_occurred_when_connecting_to_another_Service_Broker_or_Database_Mirroring_host_5_RuleMSSQL on Linux: A security (SSPI) error occurred when connecting to another Service Broker or Database Mirroring hostWhen 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 Linux 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.Linux.EventRule.DBEngine.A_security__SSPI__error_occurred_when_connecting_to_another_Service_Broker_or_Database_Mirroring_host_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.A_SQL_Server_Service_Broker_conversation_closed_due_to_an_error_5_RuleMSSQL on Linux: A SQL Server Service Broker conversation has been closed due to an errorThe rule triggers an alert when a SQL Server Service Broker conversation has been closed due to an error.Microsoft.SQLServer.Linux.EventRule.DBEngine.A_SQL_Server_Service_Broker_conversation_closed_due_to_an_error_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.A_SQL_Server_Service_Broker_cryptographic_operation_failed_5_RuleMSSQL on Linux: SQL Server Service Broker cryptographic operation failedThe rule triggers an alert when SQL Server Service Broker cryptographic operation fails.Microsoft.SQLServer.Linux.EventRule.DBEngine.A_SQL_Server_Service_Broker_cryptographic_operation_failed_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.A_SQL_Server_Service_Broker_procedure_output_results_5_RuleMSSQL on Linux: A SQL Server Service Broker procedure output resultsA stored procedure, which was internally activated by SQL Server Service Broker, output results. Internal procedures should not output results. The event in the Linux 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.Linux.EventRule.DBEngine.A_SQL_Server_Service_Broker_procedure_output_results_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionFalse00TrueInformationLowTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Backup_device_failed___Operating_system_error_1_5_RuleMSSQL on Linux: Backup device failed - Operating system errorThis 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.Linux.EventRule.DBEngine.Backup_device_failed___Operating_system_error_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Cannot_determine_the_service_account_for_SQL_Server_instance_1_5_RuleMSSQL on Linux: Cannot determine the service account for SQL Server instanceThis 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.Linux.EventRule.DBEngine.Cannot_determine_the_service_account_for_SQL_Server_instance_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Cannot_open_backup_device.__1_5_RuleMSSQL on Linux: 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.Linux.EventRule.DBEngine.Cannot_open_backup_device.__1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Cannot_open_user_default_database._Login_failed_1_5_RuleMSSQL on Linux: Cannot open user default database. Login failedWhen 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.Linux.EventRule.DBEngine.Cannot_open_user_default_database._Login_failed_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Cannot_recover_the_master_database._Exiting_1_5_RuleMSSQL on Linux: Cannot recover the master database. Exiting.The master database is not in a recoverable state.Microsoft.SQLServer.Linux.EventRule.DBEngine.Cannot_recover_the_master_database._Exiting_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Cannot_start_service_broker_activation_manager_5_RuleMSSQL on Linux: Cannot start service broker activation managerThe rule triggers an alert when service broker fails to start the activation manager.Microsoft.SQLServer.Linux.EventRule.DBEngine.Cannot_start_service_broker_activation_manager_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Cannot_start_service_broker_manager_5_RuleMSSQL on Linux: Cannot start service broker managerThe rule triggers an alert when SQL Server cannot start service broker manager.Microsoft.SQLServer.Linux.EventRule.DBEngine.Cannot_start_service_broker_manager_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Cannot_start_service_broker_manager_due_to_operating_system_error_5_RuleMSSQL on Linux: Cannot start service broker manager due to operating system errorThe rule triggers an alert when SQL Server cannot start service broker manager due to operating system error.Microsoft.SQLServer.Linux.EventRule.DBEngine.Cannot_start_service_broker_manager_due_to_operating_system_error_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Cannot_start_service_broker_security_manager_5_RuleMSSQL on Linux: Cannot start service broker security managerService Broker security manger could not start.Microsoft.SQLServer.Linux.EventRule.DBEngine.Cannot_start_service_broker_security_manager_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Cannot_start_SQL_Server_Service_Broker_on_Database_5_RuleMSSQL on Linux: Cannot start SQL Server Service Broker on a databaseThe rule triggers an alert when SQL Server cannot start Service Broker on a database.Microsoft.SQLServer.Linux.EventRule.DBEngine.Cannot_start_SQL_Server_Service_Broker_on_Database_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.CHECKTABLE_processing_of_object_encountered_page_twice._Possible_internal_error_or_allocation_fault_1_5_RuleMSSQL on Linux: CHECKTABLE processing of object encountered page twice. Possible internal error or allocation faultPage P_ID was encountered twice during the course of the scan.Microsoft.SQLServer.Linux.EventRule.DBEngine.CHECKTABLE_processing_of_object_encountered_page_twice._Possible_internal_error_or_allocation_fault_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.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_RuleMSSQL on Linux: 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.Linux.EventRule.DBEngine.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_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Check_sum_failure_while_page_in_cache_id832MSSQL on Linux: Checksum failure while page in cacheIt is detected that a database page has been unexpectedly modified while in cache (by verifying the page checksum).Microsoft.SQLServer.Linux.EventRule.DBEngine.Check_sum_failure_while_page_in_cache_id832Microsoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorHighTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Common_Language_Runtime__CLR__not_installed_properly_5_RuleMSSQL on Linux: Common Language Runtime (CLR) not installed properlyThis installation of the Common Language Runtime (CLR) is corrupted. The CLR is installed with the Microsoft .NET Framework.Microsoft.SQLServer.Linux.EventRule.DBEngine.Common_Language_Runtime__CLR__not_installed_properly_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Conflict_table__does_not_exist_1_5_RuleMSSQL on Linux: Conflict table does not existThis 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.Linux.EventRule.DBEngine.Conflict_table__does_not_exist_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Could_not_allocate_new_page_for_database_._There_are_no_more_pages_available_in_filegroup.1_5_RuleMSSQL on Linux: 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.Linux.EventRule.DBEngine.Could_not_allocate_new_page_for_database_._There_are_no_more_pages_available_in_filegroup.1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Could_not_allocate_space_for_object__in_database__because_the__filegroup_is_full_1_5_RuleMSSQL on Linux: Could not allocate space for object in database because the Filegroup is fullThe specified Filegroup has run out of free space.Microsoft.SQLServer.Linux.EventRule.DBEngine.Could_not_allocate_space_for_object__in_database__because_the__filegroup_is_full_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Could_not_connect_to_server_because_it_is_not_defined_as_a_remote_login_at_the_server_1_5_RuleMSSQL on Linux: Could not connect to server because it is not defined as a remote login at the serverSetting 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.Linux.EventRule.DBEngine.Could_not_connect_to_server_because_it_is_not_defined_as_a_remote_login_at_the_server_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Could_not_create_an_instance_of_OLE_DB_provider_1_5_RuleMSSQL on Linux: Could not create an instance of OLE DB providerThe 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.Linux.EventRule.DBEngine.Could_not_create_an_instance_of_OLE_DB_provider_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Could_not_create_AppDomain_manager_5_RuleMSSQL on Linux: Could not create AppDomain managerThe rule triggers an alert when SQL Server fails to create an application domain managerMicrosoft.SQLServer.Linux.EventRule.DBEngine.Could_not_create_AppDomain_manager_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Could_not_create_a_statement_object_using_OLE_DB_provider_1_5_RuleMSSQL on Linux: Could not create a statement object using OLE DB providerThe 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.Linux.EventRule.DBEngine.Could_not_create_a_statement_object_using_OLE_DB_provider_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Could_not_do_cleanup_for_the_killed_process_1_5_RuleMSSQL on Linux: Could not do cleanup for the killed processThis error message occurs when another error caused a user connection to terminate abnormally.Microsoft.SQLServer.Linux.EventRule.DBEngine.Could_not_do_cleanup_for_the_killed_process_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Could_not_find_CHECK_constraint_although_the_table_is_flagged_as_having_one_1_5_RuleMSSQL on Linux: Could not find CHECK constraint, although the table is flagged as having oneThis 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.Linux.EventRule.DBEngine.Could_not_find_CHECK_constraint_although_the_table_is_flagged_as_having_one_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Could_not_find_filegroup_ID_in_sys.filegroups_for_database_5_RuleMSSQL on Linux: Could not find Filegroup ID in sys.Filegroups for databaseThe 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.Linux.EventRule.DBEngine.Could_not_find_filegroup_ID_in_sys.filegroups_for_database_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Could_not_find_FOREIGN_KEY_constraints_for_table_although_the_table_is_flagged_as_having_them_1_5_RuleMSSQL on Linux: Could not find FOREIGN KEY constraints for table, although the table is flagged as having themThis 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.Linux.EventRule.DBEngine.Could_not_find_FOREIGN_KEY_constraints_for_table_although_the_table_is_flagged_as_having_them_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Could_not_mark_database_as_suspect._Getnext_NC_scan_on_sysdatabases.dbid_failed_1_5_RuleMSSQL on Linux: Could not mark database as suspect. Getnext NC scan on sysdatabases.dbid failedThe 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.Linux.EventRule.DBEngine.Could_not_mark_database_as_suspect._Getnext_NC_scan_on_sysdatabases.dbid_failed_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Could_not_obtain_exclusive_lock_on_database_5_RuleMSSQL on Linux: Could not obtain exclusive lock on databaseYou 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.Linux.EventRule.DBEngine.Could_not_obtain_exclusive_lock_on_database_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Could_not_open_device_1_5_RuleMSSQL on Linux: Failed to open primary database fileAn operating system error occurred when opening the primary file of a database. The error message contains the specific operating system error encountered.Microsoft.SQLServer.Linux.EventRule.DBEngine.Could_not_open_device_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorHighTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Could_not_open_error_log_file_1_5_RuleMSSQL on Linux: Could not open error log fileWhen 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 Linux application log (for each installation attempt).Microsoft.SQLServer.Linux.EventRule.DBEngine.Could_not_open_error_log_file_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Could_not_open_FCB_for_invalid_file_in_database__1_5_RuleMSSQL on Linux: Invalid reference to File IDThis error occurs when SQL Server uses an invalid file ID while performing some operation. This error can occur for several different scenarios.Microsoft.SQLServer.Linux.EventRule.DBEngine.Could_not_open_FCB_for_invalid_file_in_database__1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorHighTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Could_not_open_referenced_table_1_5_RuleMSSQL on Linux: Could not open referenced tableYou 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.Linux.EventRule.DBEngine.Could_not_open_referenced_table_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Could_not_open_tempdb.__Cannot_continue_1_5_RuleMSSQL on Linux: Could not open tempdb. Cannot continueThe tempdb database could not be opened. The possible reasons for this could include:Microsoft.SQLServer.Linux.EventRule.DBEngine.Could_not_open_tempdb.__Cannot_continue_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Could_not_read_and_latch_page_1_5_RuleMSSQL on Linux: Could not read and latch pageThe 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.Linux.EventRule.DBEngine.Could_not_read_and_latch_page_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Could_not_recover_database_due_to_unresolved_transaction_outcomes_1_5_RuleMSSQL on Linux: Could not recover database due to unresolved transaction outcomesThe 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.Linux.EventRule.DBEngine.Could_not_recover_database_due_to_unresolved_transaction_outcomes_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Could_not_resolve_the_referenced_column_name_in_table_1_5_RuleMSSQL on Linux: Could not resolve the referenced column name in tableThis 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.Linux.EventRule.DBEngine.Could_not_resolve_the_referenced_column_name_in_table_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Could_not_write_a_CHECKPOINT_record_in_database_because_the_log_is_out_of_space_1_5_RuleMSSQL on Linux: Could not write a CHECKPOINT record in database because the log is out of spaceThe 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.Linux.EventRule.DBEngine.Could_not_write_a_CHECKPOINT_record_in_database_because_the_log_is_out_of_space_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.CREATE_DATABASE_failed._Could_not_allocate_enough_disk_space_for_a_new_database_on_the_named_disks_1_5_RuleMSSQL on Linux: CREATE DATABASE failed. Could not allocate enough disk space for a new database on the named disksThis error occurs when there is not enough space on the device to create the model database.Microsoft.SQLServer.Linux.EventRule.DBEngine.CREATE_DATABASE_failed._Could_not_allocate_enough_disk_space_for_a_new_database_on_the_named_disks_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Database_Backup_Failed_To_Complete_1_5_RuleMSSQL on Linux: Database Backup Failed To CompleteBACKUP failed to complete the command.Microsoft.SQLServer.Linux.EventRule.DBEngine.Database_Backup_Failed_To_Complete_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Database_cannot_be_opened_due_to_inaccessible_files_or_insufficient_memory_or_disk_space._See_the_SQL_Server_errorlog_for_details_1_5_RuleMSSQL on Linux: Database cannot be opened due to inaccessible files or insufficient memory or disk spaceError 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.Linux.EventRule.DBEngine.Database_cannot_be_opened_due_to_inaccessible_files_or_insufficient_memory_or_disk_space._See_the_SQL_Server_errorlog_for_details_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Database_could_not_recover_1_5_RuleMSSQL on Linux: Failure occurred during database recoveryThis error occurs when SQL Server fails to recover a database successfully when it is brought online.Microsoft.SQLServer.Linux.EventRule.DBEngine.Database_could_not_recover_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorHighTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Database_log_file_is_full._Back_up_the_transaction_log_for_the_database_to_free_up_some_log_space_1_5_RuleMSSQL on Linux: Database log file is full. Back up the transaction log for the database to free up some log spaceThe specified transaction log file has run out of free space.Microsoft.SQLServer.Linux.EventRule.DBEngine.Database_log_file_is_full._Back_up_the_transaction_log_for_the_database_to_free_up_some_log_space_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.DBCC_executed_found_and_not_repaired_errors_RuleMSSQL on Linux: Database consistency errors foundThis message indicates a database consistency check has encountered errors and none or not all of the errors were repaired.Microsoft.SQLServer.Linux.EventRule.DBEngine.DBCC_executed_found_and_not_repaired_errors_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorHighTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.DBCC_executed_found_and_repaired_errors_RuleMSSQL on Linux: Database consistency errors found and repairedThis message indicates a database consistency check has encountered errors and all of the errors were repaired.Microsoft.SQLServer.Linux.EventRule.DBEngine.DBCC_executed_found_and_repaired_errors_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorHighTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.DBCC_executed_found_no_errors_RuleMSSQL on Linux: Database consistency check performed with no errorsThis message indicates a database consistency check has been run but no errors were encountered.Microsoft.SQLServer.Linux.EventRule.DBEngine.DBCC_executed_found_no_errors_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueInformationLowTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Descriptor_for_object_in_database_not_found_in_the_hash_table_during_attempt_to_unhash_it_1_5_RuleMSSQL on Linux: Descriptor for object in database not found in the hash table during attempt to unhash itA temporary table could not be found. The specific object ID will be available in the Linux application log as event ID 617.Microsoft.SQLServer.Linux.EventRule.DBEngine.Descriptor_for_object_in_database_not_found_in_the_hash_table_during_attempt_to_unhash_it_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Error_while_undoing_logged_operation_in_database__1_5_RuleMSSQL on Linux: Error while undoing logged operation in databaseThe 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.Linux.EventRule.DBEngine.Error_while_undoing_logged_operation_in_database__1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.EventCollectionRule.DBEngine.CannotCreateFileMSSQL on Linux: Cannot create fileSQL Server cannot create file because the file already exists.Microsoft.SQLServer.Linux.EventRule.DBEngine.EventCollectionRule.DBEngine.CannotCreateFileMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.EventCollectionRule.DBEngine.CreateFileEncounteredOperatingSystemErrorMSSQL on Linux: CREATE FILE encountered operating system errorCREATE FILE encountered operating system error.Microsoft.SQLServer.Linux.EventRule.DBEngine.EventCollectionRule.DBEngine.CreateFileEncounteredOperatingSystemErrorMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.EventCollectionRule.DBEngine.SQLServerOutOfMemoryMSSQL on Linux: SQL Server Out Of MemorySQL Server has failed to allocate the sufficient amount of memory to run the query.Microsoft.SQLServer.Linux.EventRule.DBEngine.EventCollectionRule.DBEngine.SQLServerOutOfMemoryMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.EventCollectionRule.DBEngine.UnableToOpenThePhysicalFileMSSQL on Linux: Unable to open the physical fileSQL Server has failed to open the physical file..Microsoft.SQLServer.Linux.EventRule.DBEngine.EventCollectionRule.DBEngine.UnableToOpenThePhysicalFileMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Failed_to_add_column__to_table__1_5_RuleMSSQL on Linux: Failed to add column to tablesp_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 be either 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.Linux.EventRule.DBEngine.Failed_to_add_column__to_table__1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Failed_to_allocate_memory_for_Common_Language_Runtime__CLR__5_RuleMSSQL on Linux: 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.Linux.EventRule.DBEngine.Failed_to_allocate_memory_for_Common_Language_Runtime__CLR__5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Failed_to_create_AppDomain_5_RuleMSSQL on Linux: Failed to create AppDomainThe 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.Linux.EventRule.DBEngine.Failed_to_create_AppDomain_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Failed_to_drop_column__from_table__1_5_RuleMSSQL on Linux: Failed to drop column from tablesp_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.Linux.EventRule.DBEngine.Failed_to_drop_column__from_table__1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Failed_to_finish_full_text_operation._The_filegroup_is_empty_read_only_or_not_online_5_RuleMSSQL on Linux: Failed to finish full-text operation. The Filegroup is empty, read-only, or not onlineThe full-text operation did not finish because the Filegroup is empty, read-only, or not online.Microsoft.SQLServer.Linux.EventRule.DBEngine.Failed_to_finish_full_text_operation._The_filegroup_is_empty_read_only_or_not_online_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Failed_to_initialize_the_Common_Language_Runtime__CLR__due_to_memory_pressure_5_RuleMSSQL on Linux: Failed to initialize the Common Language Runtime (CLR) due to memory pressureLinux could not allocate memory for the Microsoft Common Language Runtime (CLR) to initialize.Microsoft.SQLServer.Linux.EventRule.DBEngine.Failed_to_initialize_the_Common_Language_Runtime__CLR__due_to_memory_pressure_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Failed_to_initialize_the_Common_Language_Runtime__CLR__with_HRESULT_1_5_RuleMSSQL on Linux: Failed to initialize the Common Language Runtime (CLR) with HRESULT (6511)The rule triggers an alert when an assembly or application fails to start and logs an HRESULT error.Microsoft.SQLServer.Linux.EventRule.DBEngine.Failed_to_initialize_the_Common_Language_Runtime__CLR__with_HRESULT_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Failed_to_initialize_the_Common_Language_Runtime__CLR__with_HRESULT_5_RuleMSSQL on Linux: Failed to initialize the Common Language Runtime (CLR) with HRESULT (6512)The rule triggers an alert when an assembly or an application fails to start and logs an HRESULT error. The Linux application log may contain an information about specific HRESULT.Microsoft.SQLServer.Linux.EventRule.DBEngine.Failed_to_initialize_the_Common_Language_Runtime__CLR__with_HRESULT_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Failed_to_restore_master_database._Shutting_down_SQL_Server_5_RuleMSSQL on Linux: Failed to restore master database. Shutting down SQL ServerThe 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.Linux.EventRule.DBEngine.Failed_to_restore_master_database._Shutting_down_SQL_Server_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Full_Text_Search___An_unknown_full_text_failure_occurred_1_5_RuleMSSQL on Linux: Full Text Search: An unknown full-text failure occurredThis error can occur in various circumstances. It is often related to permissions or missing files.Microsoft.SQLServer.Linux.EventRule.DBEngine.Full_Text_Search___An_unknown_full_text_failure_occurred_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Full_Text_Search___Could_not_find_full_text_index_for_database_1_5_RuleMSSQL on Linux: Full Text Search: Could not find full-text index for databaseThe specified full-text index is unavailable.Microsoft.SQLServer.Linux.EventRule.DBEngine.Full_Text_Search___Could_not_find_full_text_index_for_database_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Full_Text_Search___Full_text_catalog_is_in_a_unusable_state._Drop_and_re_create_this_full_text_catalog_1_5_RuleMSSQL on Linux: Full Text Search: Full-text catalog is in an unusable state. Drop and re-create this full-text catalogThe 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.Linux.EventRule.DBEngine.Full_Text_Search___Full_text_catalog_is_in_a_unusable_state._Drop_and_re_create_this_full_text_catalog_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Full_Text_Search___Full_text_catalog_lacks_sufficient_disk_space_to_complete_this_operation_1_5_RuleMSSQL on Linux: Full Text Search: Full-text catalog lacks sufficient disk space to complete this operationThere is not enough disk space to hold the full-text catalog.Microsoft.SQLServer.Linux.EventRule.DBEngine.Full_Text_Search___Full_text_catalog_lacks_sufficient_disk_space_to_complete_this_operation_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Full_Text_Search___Full_Text_Search_is_not_enabled_for_the_current_database._Use_sp_fulltext_database_to_enable_Full_Text_Search_1_5_RuleMSSQL on Linux: Full Text Search: Full-Text Search is not enabled for the current database. Use sp_fulltext_database to enable Full-Text SearchYou 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.Linux.EventRule.DBEngine.Full_Text_Search___Full_Text_Search_is_not_enabled_for_the_current_database._Use_sp_fulltext_database_to_enable_Full_Text_Search_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Full_Text_Search___Search_on_full_text_catalog_failed_with_unknown_result_1_5_RuleMSSQL on Linux: Full Text Search: Search on full-text catalog failed with unknown resultThe full-text query failed for an unspecified reason.Microsoft.SQLServer.Linux.EventRule.DBEngine.Full_Text_Search___Search_on_full_text_catalog_failed_with_unknown_result_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Indexed_view_does_not_contain_all_rows_that_the_view_definition_produces.__Refer_to_Books_Online_for_more_information_on_this_error.5_RuleMSSQL on Linux: 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.Linux.EventRule.DBEngine.Indexed_view_does_not_contain_all_rows_that_the_view_definition_produces.__Refer_to_Books_Online_for_more_information_on_this_error.5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Internal_Query_Processor_Error__The_query_processor_could_not_obtain_access_to_a_required_interface_1_5_RuleMSSQL on Linux: Internal Query Processor Error: The query processor could not obtain access to a required interfaceThis is an internal query processor error.Microsoft.SQLServer.Linux.EventRule.DBEngine.Internal_Query_Processor_Error__The_query_processor_could_not_obtain_access_to_a_required_interface_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Internal_Query_Processor_Error__The_query_processor_encountered_an_internal_limit_overflow_1_5_RuleMSSQL on Linux: Internal Query Processor Error: The query processor encountered an internal limit overflowThis is an internal query processor error.Microsoft.SQLServer.Linux.EventRule.DBEngine.Internal_Query_Processor_Error__The_query_processor_encountered_an_internal_limit_overflow_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Internal_Query_Processor_Error__The_query_processor_encountered_an_unexpected_error_during_execution_1_5_RuleMSSQL on Linux: Internal Query Processor Error: The query processor encountered an unexpected error during executionThis is an internal query processor error.Microsoft.SQLServer.Linux.EventRule.DBEngine.Internal_Query_Processor_Error__The_query_processor_encountered_an_unexpected_error_during_execution_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Internal_Query_Processor_Error__The_query_processor_encountered_an_unexpected_error_during_the_processing_of_a_remote_query_phase_1_5_RuleMSSQL on Linux: Internal Query Processor Error: The query processor encountered an unexpected error during the processing of a remote query phaseThis is an internal query processor error.Microsoft.SQLServer.Linux.EventRule.DBEngine.Internal_Query_Processor_Error__The_query_processor_encountered_an_unexpected_error_during_the_processing_of_a_remote_query_phase_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Internal_Query_Processor_Error__The_query_processor_ran_out_of_stack_space_during_query_optimization_1_5_RuleMSSQL on Linux: Internal Query Processor Error: The query processor ran out of stack space during query optimizationThe 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.Linux.EventRule.DBEngine.Internal_Query_Processor_Error__The_query_processor_ran_out_of_stack_space_during_query_optimization_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Invalid_reference_to_LOB_page_id7105MSSQL on Linux: Invalid reference to LOB pageThis 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.Linux.EventRule.DBEngine.Invalid_reference_to_LOB_page_id7105Microsoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorHighTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.IORequestsTakingLongerThen15SecondsToCompleteMSSQL on Linux: I/O request taking longer than 15 seconds to completeI/O request has taken longer than 15 seconds to complete. This may indicate an SQL Server I/O bottlenecks. SQL Server performance highly relies on the disk performance. Note: this rule is disabled by default. Please use overrides to enable it when necessary.Microsoft.SQLServer.Linux.EventRule.DBEngine.IORequestsTakingLongerThen15SecondsToCompleteMicrosoft.SQLServer.Linux.DBEngineEventCollectionFalse00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.IO_Completion_Listener_Worker_appears_to_be_non_yielding_on_Node_5_RuleMSSQL on Linux: IO Completion Listener Worker appears to be non-yielding on NodeI/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.Linux.EventRule.DBEngine.IO_Completion_Listener_Worker_appears_to_be_non_yielding_on_Node_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionFalse00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Logical_consistency_error_after_performing_IO_on_page_id824MSSQL on Linux: Logical consistency error after performing I/O on pageA 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.Linux.EventRule.DBEngine.Logical_consistency_error_after_performing_IO_on_page_id824Microsoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorHighTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Logical_page_in_database_is_already_hashed_1_5_RuleMSSQL on Linux: Logical page in database is already hashedThis 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.Linux.EventRule.DBEngine.Logical_page_in_database_is_already_hashed_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Login_failed._The_workstation_licensing_limit_for_SQL_Server_access_has_already_been_reached_5_RuleMSSQL on Linux: Login failed. The workstation licensing limit for SQL Server access has already been reachedSQL Server will not provide connections to workstations after the licensing limit has been reached.Microsoft.SQLServer.Linux.EventRule.DBEngine.Login_failed._The_workstation_licensing_limit_for_SQL_Server_access_has_already_been_reached_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Login_failed__AccountMSSQL on Linux: Login failedWhen 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)".Microsoft.SQLServer.Linux.EventRule.DBEngine.Login_failed__AccountMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Login_failed__Account_locked_out_5_RuleMSSQL on Linux: Login failed: Account locked outA user attempted to log into the network with an account that has been locked out. The Linux security log will identify the user name under MSSQLSERVER event ID 18486.Microsoft.SQLServer.Linux.EventRule.DBEngine.Login_failed__Account_locked_out_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Login_failed__Error_during_validation_5_RuleMSSQL on Linux: Login failed: Error during validationA user attempted to log in to SQL Server. An unexpected error occurred during validation. The Linux security log will identify the user name and error ID under MSSQLSERVER event ID 18468.Microsoft.SQLServer.Linux.EventRule.DBEngine.Login_failed__Error_during_validation_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Login_failed__Password_cannot_be_used_at_this_time_5_RuleMSSQL on Linux: Login failed: Password cannot be used at this timeA user attempted to change the password, but the proposed password could not be used at this time. The Linux security log will identify the user name under MSSQLSERVER event ID 18463.Microsoft.SQLServer.Linux.EventRule.DBEngine.Login_failed__Password_cannot_be_used_at_this_time_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Login_failed__Password_expired_5_RuleMSSQL on Linux: Login failed: Password expiredA user attempted to log into SQL Server with an expired password. The Linux security log will identify the user name under event ID 18487.Microsoft.SQLServer.Linux.EventRule.DBEngine.Login_failed__Password_expired_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Login_failed__Password_must_be_changed_5_RuleMSSQL on Linux: Login failed: Password must be changedA 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 Linux security log under MSSQLSERVER event ID 18488.Microsoft.SQLServer.Linux.EventRule.DBEngine.Login_failed__Password_must_be_changed_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Login_failed__Password_too_long_5_RuleMSSQL on Linux: Login failed: Password too longA user attempted to create a password, but the proposed password was too long. The Linux security log will identify the user name under MSSQLSERVER event ID 18465.Microsoft.SQLServer.Linux.EventRule.DBEngine.Login_failed__Password_too_long_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Login_failed__Password_too_short_5_RuleMSSQL on Linux: Login failed: Password too shortA user attempted to change the password, but the proposed password was too short. The Linux security log will identify the user name under MSSQLSERVER event ID 18464.Microsoft.SQLServer.Linux.EventRule.DBEngine.Login_failed__Password_too_short_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Login_failed__Password_too_simple_5_RuleMSSQL on Linux: Login failed: Password too simpleA user attempted to create a password, but the proposed password did not meet the Linux password complexity requirements policy. These are defined in the Password must meet complexity requirements policy setting. The Linux security log will identify the user name under MSSQLSERVER event ID 18466.Microsoft.SQLServer.Linux.EventRule.DBEngine.Login_failed__Password_too_simple_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Log_Backup_Failed_to_Complete_1_5_RuleMSSQL on Linux: Log Backup Failed to CompleteThis 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 Linux application log.Microsoft.SQLServer.Linux.EventRule.DBEngine.Log_Backup_Failed_to_Complete_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Maximum_limit_for_connections_has_been_reached_1_5_RuleMSSQL on Linux: Maximum limit for connections has been reachedBy 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.Linux.EventRule.DBEngine.Maximum_limit_for_connections_has_been_reached_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.No_slots_are_free_to_keep_buffers_for_table__1_5_RuleMSSQL on Linux: No slots are free to keep buffers for tableThis is raised when SQL Server has an internal error.Microsoft.SQLServer.Linux.EventRule.DBEngine.No_slots_are_free_to_keep_buffers_for_table__1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.One_or_more_indexes_are_damaged_and_must_be_repaired_or_dropped_1_5_RuleMSSQL on Linux: One or more indexes are damaged and must be repaired or droppedThis error provides more details about the problem described in error 8952. See that error for an explanation.Microsoft.SQLServer.Linux.EventRule.DBEngine.One_or_more_indexes_are_damaged_and_must_be_repaired_or_dropped_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Operating_system_error_during_creation_opening_of_physical_device_1_5_RuleMSSQL on Linux: Failed to open database or transaction log fileAn 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.Linux.EventRule.DBEngine.Operating_system_error_during_creation_opening_of_physical_device_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorHighTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Operating_System_error_encountered_1_5_RuleMSSQL on Linux: Operating System error encounteredThis 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 usually seen in conjunction with other errors.Microsoft.SQLServer.Linux.EventRule.DBEngine.Operating_System_error_encountered_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Operating_system_error_on_a_device_1_5_RuleMSSQL on Linux: Operating system error on a deviceThe backup device cannot be opened.Microsoft.SQLServer.Linux.EventRule.DBEngine.Operating_system_error_on_a_device_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Optimized_concurrent_query_limit_has_been_exceeded_1_5_RuleMSSQL on Linux: Optimized concurrent query limit has been exceededYou 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.Linux.EventRule.DBEngine.Optimized_concurrent_query_limit_has_been_exceeded_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.OSError_Occurred_While_Performing_IO_onpage_id823MSSQL on Linux: OS Error occurred while performing I/O on pageAn operating system error occurred when reading or writing a database page. The error message contains the specific operating system error encountered.Microsoft.SQLServer.Linux.EventRule.DBEngine.OSError_Occurred_While_Performing_IO_onpage_id823Microsoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorHighTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Permission_denied_on_object_1_5_RuleMSSQL on Linux: Permission denied on objectThis 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.Linux.EventRule.DBEngine.Permission_denied_on_object_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.PhysicalFileAccessErrorMSSQL on Linux: Physical file access errorA file activation error occurred. The physical file name may be incorrect while creating the database. Note: this rule is disabled by default. Please use overrides to enable it when necessary.Microsoft.SQLServer.Linux.EventRule.DBEngine.PhysicalFileAccessErrorMicrosoft.SQLServer.Linux.DBEngineEventCollectionFalse00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Potential_deadlocks_exist_on_all_schedulers_on_Node_5_RuleMSSQL on Linux: Potential deadlocks exist on all schedulers on NodeThis message is raised when the server fails to respond to new queries within a certain time limit.Microsoft.SQLServer.Linux.EventRule.DBEngine.Potential_deadlocks_exist_on_all_schedulers_on_Node_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Process_Worker_appears_to_be_non_yielding_on_Scheduler_5_RuleMSSQL on Linux: Process Worker appears to be non-yielding on SchedulerThis 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.Linux.EventRule.DBEngine.Process_Worker_appears_to_be_non_yielding_on_Scheduler_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionFalse00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Recovery_of_database__detected_possible_identity_value_inconsistency_in_table_1_5_RuleMSSQL on Linux: Recovery of database detected possible identity value inconsistency in tableThe database recovery process could not determine the current identity value for the specified table.Microsoft.SQLServer.Linux.EventRule.DBEngine.Recovery_of_database__detected_possible_identity_value_inconsistency_in_table_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.RESTORE_could_not_start_database_1_5_RuleMSSQL on Linux: RESTORE could not start databaseInternal structures could not be created during the database RESTORE. This is usually the side effect of another error.Microsoft.SQLServer.Linux.EventRule.DBEngine.RESTORE_could_not_start_database_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Rule.XTP.BackgroundThreadErrorMSSQL on Linux: XTP Background Thread ErrorThe rule listens to event 41354 and raises a warning alert if the event is added to the log.Microsoft.SQLServer.Linux.EventRule.DBEngine.Rule.XTP.BackgroundThreadErrorMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Rule.XTP.BackgroundThreadErrorLogMSSQL on Linux: XTP Background Thread Error LogThe rule listens to event 41355 and raises a warning alert if the event is added to the log.Microsoft.SQLServer.Linux.EventRule.DBEngine.Rule.XTP.BackgroundThreadErrorLogMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Rule.XTP.CompilerFailureMSSQL on Linux: XTP Compiler FailureThe rule listens to event 41313 and raises a warning alert if the event is added to the log.Microsoft.SQLServer.Linux.EventRule.DBEngine.Rule.XTP.CompilerFailureMicrosoft.SQLServer.Linux.DBEngineEventCollectionFalse00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Rule.XTP.InsufficientDiskSpaceMSSQL on Linux: XTP Insufficient Disk SpaceThe rule listens to event 41822 and raises a critical alert if the event is added to the log.Microsoft.SQLServer.Linux.EventRule.DBEngine.Rule.XTP.InsufficientDiskSpaceMicrosoft.SQLServer.Linux.DBEngineEventCollectionFalse00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Rule.XTP.UnableCallCompilerMSSQL on Linux: XTP Unable Call CompilerThe rule listens to event 41312 and raises a warning alert if the event is added to the log.Microsoft.SQLServer.Linux.EventRule.DBEngine.Rule.XTP.UnableCallCompilerMicrosoft.SQLServer.Linux.DBEngineEventCollectionFalse00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Rule.XTP.UnableLoadCompiledDllMSSQL on Linux: XTP Unable Load Compiled DllThe rule listens to event 41309 and raises a warning alert if the event is added to the log.Microsoft.SQLServer.Linux.EventRule.DBEngine.Rule.XTP.UnableLoadCompiledDllMicrosoft.SQLServer.Linux.DBEngineEventCollectionFalse00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.ServiceRestartMSSQL on Linux: SQL Server DB Engine is restartedDetects SQL Server DB Engine restart. Note: This rule is disabled by default. Please use overrides to enable it when necessary.Microsoft.SQLServer.Linux.EventRule.DBEngine.ServiceRestartMicrosoft.SQLServer.Linux.DBEngineAvailabilityHealthFalse00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Service_Broker_was_not_able_to_allocate_memory_for_cryptographic_operations_5_RuleMSSQL on Linux: Service Broker was not able to allocate memory for cryptographic operationsThe rule triggers an alert when SQL Server Service Broker is not able to allocate memory for cryptographic operations.Microsoft.SQLServer.Linux.EventRule.DBEngine.Service_Broker_was_not_able_to_allocate_memory_for_cryptographic_operations_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.SQL_Server_Assertion_1_5_RuleMSSQL on Linux: SQL Server Assertion (17066)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.Linux.EventRule.DBEngine.SQL_Server_Assertion_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.SQL_Server_Assertion_2_5_RuleMSSQL on Linux: SQL Server Assertion (17067)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.Linux.EventRule.DBEngine.SQL_Server_Assertion_2_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.SQL_Server_Assertion_3_5_RuleMSSQL on Linux: SQL Server Assertion (17065)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.Linux.EventRule.DBEngine.SQL_Server_Assertion_3_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.SQL_Server_cannot_start_the_Service_Broker_event_handler_5_RuleMSSQL on Linux: SQL Server cannot start the Service Broker event handlerSQL Server Service Broker cannot start the Service Broker event handler.Microsoft.SQLServer.Linux.EventRule.DBEngine.SQL_Server_cannot_start_the_Service_Broker_event_handler_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.SQL_Server_could_not_allocate_enough_memory_to_start_Service_Broker_task_manager_5_RuleMSSQL on Linux: SQL Server could not allocate enough memory to start Service Broker task managerSQL Server Service Broker cannot start Service Broker task manager.Microsoft.SQLServer.Linux.EventRule.DBEngine.SQL_Server_could_not_allocate_enough_memory_to_start_Service_Broker_task_manager_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.SQL_Server_Service_Broker_cannot_use_RC4_encryption_algorithm_when_running_in_FIPS_compliance_mode_5_RuleMSSQL on Linux: SQL Server Service Broker cannot use RC4 encryption algorithm when running in FIPS compliance modeSQL 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.Linux.EventRule.DBEngine.SQL_Server_Service_Broker_cannot_use_RC4_encryption_algorithm_when_running_in_FIPS_compliance_mode_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.SQL_Server_Service_Broker_could_not_query_the_FIPS_compliance_mode_flag_from_the_registry_5_RuleMSSQL on Linux: SQL Server Service Broker could not query the FIPS compliance mode flag from the registryThe rule triggers an alert when SQL Server Service Broker could not query the FIPS compliance mode flag from the registry.Microsoft.SQLServer.Linux.EventRule.DBEngine.SQL_Server_Service_Broker_could_not_query_the_FIPS_compliance_mode_flag_from_the_registry_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.SQL_Server_Service_Broker_Manager_has_shutdown_5_RuleMSSQL on Linux: SQL Server Service Broker Manager has shutdownThe 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.Linux.EventRule.DBEngine.SQL_Server_Service_Broker_Manager_has_shutdown_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionFalse00TrueInformationNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.SQL_Server_Service_Broker_or_Database_Mirroring_is_running_in_FIPS_compliance_mode_5_RuleMSSQL on Linux: SQL Server Service Broker or Database Mirroring is running in FIPS compliance modeThe 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.Linux.EventRule.DBEngine.SQL_Server_Service_Broker_or_Database_Mirroring_is_running_in_FIPS_compliance_mode_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionFalse00TrueInformationLowTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.SQL_Server_Service_Broker_or_Database_Mirroring_Transport_stopped_5_RuleMSSQL on Linux: SQL Server Service Broker or Database Mirroring Transport stoppedThe 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.Linux.EventRule.DBEngine.SQL_Server_Service_Broker_or_Database_Mirroring_Transport_stopped_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionFalse00TrueErrorLowTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.SQL_Server_Service_Broker_or_Database_Mirror_cryptographic_call_failed_5_RuleMSSQL on Linux: SQL Server Service Broker or Database Mirror cryptographic call failedSQL Server Service Broker or Database Mirror attempted to call an operating system cryptographic function. The cryptographic function returned an error.Microsoft.SQLServer.Linux.EventRule.DBEngine.SQL_Server_Service_Broker_or_Database_Mirror_cryptographic_call_failed_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.SQL_Server_Service_Broker_transmitter_shut_down_due_to_an_exception_or_a_lack_of_memory_5_RuleMSSQL on Linux: SQL Server Service Broker transmitter shut down due to an exception or a lack of memoryThe 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.Linux.EventRule.DBEngine.SQL_Server_Service_Broker_transmitter_shut_down_due_to_an_exception_or_a_lack_of_memory_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionFalse00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.SQL_Server_shutdown_due_to_Ctrl_C_or_Ctrl_Break_signal_1_5_RuleMSSQL on Linux: SQL Server shutdown due to Ctrl-C or Ctrl-Break signalThe 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.Linux.EventRule.DBEngine.SQL_Server_shutdown_due_to_Ctrl_C_or_Ctrl_Break_signal_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.SQL_Server_SQL_Server_Service_Broker_attempted_to_use_an_unsupported_encryption_algorithm_5_RuleMSSQL on Linux: SQL Server Service Broker attempted to use an unsupported encryption algorithmThe rule triggers an alert when SQL Server Service Broker tries to use an unsupported encryption algorithm.Microsoft.SQLServer.Linux.EventRule.DBEngine.SQL_Server_SQL_Server_Service_Broker_attempted_to_use_an_unsupported_encryption_algorithm_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.SQL_Server_terminating_because_of_system_shutdown_1_5_RuleMSSQL on Linux: SQL Server terminating because of system shutdownSQL 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.Linux.EventRule.DBEngine.SQL_Server_terminating_because_of_system_shutdown_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionFalse00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Starting_without_recovery_1_5_RuleMSSQL on Linux: Starting without recoverySQL Server is starting without recovery.Microsoft.SQLServer.Linux.EventRule.DBEngine.Starting_without_recovery_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__Allocation_page_has_invalid__page_header_values.__1_5_RuleMSSQL on Linux: Table error: Allocation page has invalid page header values.The page specified has an invalid page header.Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__Allocation_page_has_invalid__page_header_values.__1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__B_tree_chain_linkage_mismatch.__1_5_RuleMSSQL on Linux: 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.Linux.EventRule.DBEngine.Table_error__B_tree_chain_linkage_mismatch.__1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__B_tree_level_mismatch_page_does_not_match_level_from_parent__1_5_RuleMSSQL on Linux: Table error: B-tree level mismatch, page does not match level from parentThere 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.Linux.EventRule.DBEngine.Table_error__B_tree_level_mismatch_page_does_not_match_level_from_parent__1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__B_tree_page_has_two_parent_nodes__1_5_RuleMSSQL on Linux: Table error: B-tree page has two parent nodesThe 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.Linux.EventRule.DBEngine.Table_error__B_tree_page_has_two_parent_nodes__1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__Column_is_not_a_valid_complex_column_1_5_RuleMSSQL on Linux: Table error: Column is not a valid complex columnA 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.Linux.EventRule.DBEngine.Table_error__Column_is_not_a_valid_complex_column_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__cross_object_chain_linkage_1_5_RuleMSSQL on Linux: Table error: cross-object chain linkageThe 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.Linux.EventRule.DBEngine.Table_error__cross_object_chain_linkage_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__Cross_object_linkage._Page_PGID_next_is_not_in_the_same_index_1_5_RuleMSSQL on Linux: Table error: Cross object linkage. Page PGID->next is not in the same indexPage P_ID is linked to page P_ID2 but the two pages are allocated to different indexes and/or objects.Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__Cross_object_linkage._Page_PGID_next_is_not_in_the_same_index_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__Cross_object_linkage_1_5_RuleMSSQL on Linux: Table error: Cross object linkageThe page P_ID1 points, in a parent-child manner, to a page (P_ID2) in a different object.Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__Cross_object_linkage_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__Cross_object_linkage__Parent_page_in_object_next_refer_to_page_not_in_the_same_object_1_5_RuleMSSQL on Linux: Table error: Cross object linkage: Parent page in object next refer to page not in the same objectThe 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.Linux.EventRule.DBEngine.Table_error__Cross_object_linkage__Parent_page_in_object_next_refer_to_page_not_in_the_same_object_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__Extent_object_is_beyond_the_range_of_this_database_1_5_RuleMSSQL on Linux: Table error: Extent object is beyond the range of this databaseP_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.Linux.EventRule.DBEngine.Table_error__Extent_object_is_beyond_the_range_of_this_database_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__Extra_or_invalid_key_1_5_RuleMSSQL on Linux: Table error: Extra or invalid keyEvery 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.Linux.EventRule.DBEngine.Table_error__Extra_or_invalid_key_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__IAM_chain_linkage_error_1_5_RuleMSSQL on Linux: Table error: IAM chain linkage errorThere 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.Linux.EventRule.DBEngine.Table_error__IAM_chain_linkage_error_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__IAM_page_is_linked_in_the_IAM_chain_for_object_1_5_RuleMSSQL on Linux: Table error: IAM page is linked in the IAM chain for objectAll 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.Linux.EventRule.DBEngine.Table_error__IAM_page_is_linked_in_the_IAM_chain_for_object_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__Index_node_page_refers_to_child_page_and_previous_child_but_they_were_not_encountered_1_5_RuleMSSQL on Linux: Table error: Index node page refers to child page and previous child, but they were not encounteredAn 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.Linux.EventRule.DBEngine.Table_error__Index_node_page_refers_to_child_page_and_previous_child_but_they_were_not_encountered_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__Object_index_page_Test_failed._Slot___Offset_is__invalid_1_5_RuleMSSQL on Linux: Table error: Object, index, page Test failed. Slot - Offset is invalidThe slot specified has an invalid offset (ADDRESS) in the page, according to the slot array.Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__Object_index_page_Test_failed._Slot___Offset_is__invalid_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__Page_allocated_to_object_was_not_seen.__Page_may_be_invalid_or_have_incorrect_object_ID_information_in_its_header_1_5_RuleMSSQL on Linux: Table error: Page allocated to object was not seen. Page may be invalid or have incorrect object ID information in its headerA 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.Linux.EventRule.DBEngine.Table_error__Page_allocated_to_object_was_not_seen.__Page_may_be_invalid_or_have_incorrect_object_ID_information_in_its_header_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__Page_in_its_header_is_allocated_by_another_object_1_5_RuleMSSQL on Linux: Table error: Page in its header is allocated by another objectA 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.Linux.EventRule.DBEngine.Table_error__Page_in_its_header_is_allocated_by_another_object_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__Page_is_missing_a_reference_from_previous_page._Possible_chain_linkage_problem_1_5_RuleMSSQL on Linux: Table error: Page is missing a reference from previous page. Possible chain linkage problemA 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.Linux.EventRule.DBEngine.Table_error__Page_is_missing_a_reference_from_previous_page._Possible_chain_linkage_problem_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__Page_is_missing_references_from_parent__unknown__and_previous_nodes._Possible_bad_root_entry_in_sysindexes_1_5_RuleMSSQL on Linux: Table error: Page is missing references from parent (unknown) and previous nodes. Possible bad root entry in sysindexesPage P_ID1 was seen, but is not linked into the B-tree it thinks it belongs to.Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__Page_is_missing_references_from_parent__unknown__and_previous_nodes._Possible_bad_root_entry_in_sysindexes_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__page_is_out_of_the_range_of_this_database_1_5_RuleMSSQL on Linux: Table error: page is out of the range of this databaseThe 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.Linux.EventRule.DBEngine.Table_error__page_is_out_of_the_range_of_this_database_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__Page_was_not_seen_in_the_scan_although_its_parent_and_previous_refer_to_it._Check_any_previous_errors_1_5_RuleMSSQL on Linux: Table error: Page was not seen in the scan although its parent and previous refer to it. Check any previous errorsA 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.Linux.EventRule.DBEngine.Table_error__Page_was_not_seen_in_the_scan_although_its_parent_and_previous_refer_to_it._Check_any_previous_errors_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__Parent_node_for_page_was_not_encountered_1_5_RuleMSSQL on Linux: Table error: Parent node for page was not encounteredPage 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.Linux.EventRule.DBEngine.Table_error__Parent_node_for_page_was_not_encountered_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__Slot_row_extends_into_free_space__1_5_RuleMSSQL on Linux: Table error: Slot, row extends into free spaceThe 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.Linux.EventRule.DBEngine.Table_error__Slot_row_extends_into_free_space__1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__Table_missing_or_invalid_key_in_index_for_the_row__1_5_RuleMSSQL on Linux: 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.Linux.EventRule.DBEngine.Table_error__Table_missing_or_invalid_key_in_index_for_the_row__1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.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_RuleMSSQL on Linux: Table error: The high key value on page is not less than the low key value in the parent, slot of the next pageA 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.Linux.EventRule.DBEngine.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_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__The_low_key_value_on_page__is_not_the_key_value_in_the_parent_1_5_RuleMSSQL on Linux: Table error: The low key value on page is not the key value in the parentA 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.Linux.EventRule.DBEngine.Table_error__The_low_key_value_on_page__is_not_the_key_value_in_the_parent_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__The_previous_link_on_page_does_not_match_the_previous_page_that_the_parent_slot_expects_for_this_page_1_5_RuleMSSQL on Linux: Table error: The previous link on page does not match the previous page that the parent, slot expects for this pageA 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.Linux.EventRule.DBEngine.Table_error__The_previous_link_on_page_does_not_match_the_previous_page_that_the_parent_slot_expects_for_this_page_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__The_text_ntext_or_image_node_at_page_is_not_referenced_1_5_RuleMSSQL on Linux: Table error: The text, ntext, or image node at page is not referencedThe text node was not referenced in any complex column in any heap or clustered index. It is effectively orphaned.Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__The_text_ntext_or_image_node_at_page_is_not_referenced_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__The_text_ntext_or_image_node_at_page__is_referenced_by_page_not_seen_in_the_scan_1_5_RuleMSSQL on Linux: Table error: The text, ntext, or image node at page is referenced by page not seen in the scanThe text node was not referenced in any complex column in any heap or clustered index. It is effectively orphaned.Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__The_text_ntext_or_image_node_at_page__is_referenced_by_page_not_seen_in_the_scan_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__The_text_ntext_or_image_node_has_wrong_type_1_5_RuleMSSQL on Linux: Table error: The text, ntext, or image node has wrong typeThe 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.Linux.EventRule.DBEngine.Table_error__The_text_ntext_or_image_node_has_wrong_type_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error__Wrong_PageId_in_the_page_header_1_5_RuleMSSQL on Linux: Table error: Wrong PageId in the page headerDBCC 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.Linux.EventRule.DBEngine.Table_error__Wrong_PageId_in_the_page_header_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error___Address_is_not_aligned_1_5_RuleMSSQL on Linux: Table error: Address is not alignedThe structure at address ADDRESS is not 4-byte aligned.Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error___Address_is_not_aligned_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error___Test_failed._Slot_overlaps_with_the_prior_row_1_5_RuleMSSQL on Linux: Table error: Test failed. Slot overlaps with the prior rowSlot 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.Linux.EventRule.DBEngine.Table_error___Test_failed._Slot_overlaps_with_the_prior_row_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error___The_next_pointer_of_refers_to_page._Neither_its_parent_were_encountered._Possible_bad_chain_linkage_1_5_RuleMSSQL on Linux: Table error: The next pointer of refers to page. Neither its parent were encountered. Possible bad chain linkageA 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.Linux.EventRule.DBEngine.Table_error___The_next_pointer_of_refers_to_page._Neither_its_parent_were_encountered._Possible_bad_chain_linkage_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table_error___Unexpected_page_type__1_5_RuleMSSQL on Linux: Table error: Unexpected page typePage 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.Linux.EventRule.DBEngine.Table_error___Unexpected_page_type__1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table__Creating_statistics_for_the_following_columns_1_5_RuleMSSQL on Linux: Table: Creating statistics for the following columnssp_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.Linux.EventRule.DBEngine.Table__Creating_statistics_for_the_following_columns_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionFalse00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Table___No_columns_without_statistics_found_1_5_RuleMSSQL on Linux: Table: No columns without statistics foundThere 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.Linux.EventRule.DBEngine.Table___No_columns_without_statistics_found_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.The_IO_operation_was_successful_after_retry_id825MSSQL on Linux: The I/O operation was successful after retryA 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.Linux.EventRule.DBEngine.The_IO_operation_was_successful_after_retry_id825Microsoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.The_log_for_database_is_not_available_1_5_RuleMSSQL on Linux: The log for database is not availableAn 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 Linux event logs.Microsoft.SQLServer.Linux.EventRule.DBEngine.The_log_for_database_is_not_available_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.The_LSN_passed_to_log_scan_in_database_is_invalid_5_RuleMSSQL on Linux: The LSN passed to log scan in database is invalidIf 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.Linux.EventRule.DBEngine.The_LSN_passed_to_log_scan_in_database_is_invalid_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.The_MSSQLServer_service_terminated_unexpectedly_3_5_RuleMSSQL on Linux: The MSSQLServer service terminated unexpectedlyThe 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.Linux.EventRule.DBEngine.The_MSSQLServer_service_terminated_unexpectedly_3_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.The_provider_reported_an_unexpected_catastrophic_failure_1_5_RuleMSSQL on Linux: The provider reported an unexpected catastrophic failureThe provider reported an unexpected catastrophic failure.Microsoft.SQLServer.Linux.EventRule.DBEngine.The_provider_reported_an_unexpected_catastrophic_failure_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.The_query_has_been_canceled_because_the_estimated_cost_of_this_query_exceeds_the_configured_threshold._Contact_the_system_administrator_1_5_RuleMSSQL on Linux: The query has been canceled because the estimated cost of this query exceeds the configured threshold. Contact the system administratorThe 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.Linux.EventRule.DBEngine.The_query_has_been_canceled_because_the_estimated_cost_of_this_query_exceeds_the_configured_threshold._Contact_the_system_administrator_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.The_query_processor_could_not_start_the_necessary_thread_resources_for_parallel_query_execution_1_5_RuleMSSQL on Linux: The query processor could not start the necessary thread resources for parallel query executionThread resources are scarce in the server.Microsoft.SQLServer.Linux.EventRule.DBEngine.The_query_processor_could_not_start_the_necessary_thread_resources_for_parallel_query_execution_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.The_server_is_too_busy_to_perform_the_backup_or_restore_operation_1_5_RuleMSSQL on Linux: The server is too busy to perform the backup or restore operationFailed 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.Linux.EventRule.DBEngine.The_server_is_too_busy_to_perform_the_backup_or_restore_operation_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.The_Service_Broker_Database_Mirroring_transport_cannot_listen_on_port_because_it_is_in_use_5_RuleMSSQL on Linux: The Service Broker/Database Mirroring transport cannot listen on port because it is in useWhen 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.Linux.EventRule.DBEngine.The_Service_Broker_Database_Mirroring_transport_cannot_listen_on_port_because_it_is_in_use_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.The_Service_Broker_Database_Mirroring_Transport_could_not_listen_for_connections_due_to_an_error_5_RuleMSSQL on Linux: The Service Broker/Database Mirroring Transport could not listen for connections due to an errorThe rule triggers an alert when Service Broker cannot listen on the specified port.Microsoft.SQLServer.Linux.EventRule.DBEngine.The_Service_Broker_Database_Mirroring_Transport_could_not_listen_for_connections_due_to_an_error_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.The_Service_Broker_or_Database_Mirroring_Transport_has_started_5_RuleMSSQL on Linux: The Service Broker or Database Mirroring Transport has startedSQL Server Service Broker or Database Mirroring transport has started. The Linux application log specifies whether the error was recorded by Service Broker or Database Mirroring the application name. This message is logged in the Linux application log as MSSQLSERVER event ID 9690. Note: This rule is disabled by default. Please use overrides to enable it when necessary.Microsoft.SQLServer.Linux.EventRule.DBEngine.The_Service_Broker_or_Database_Mirroring_Transport_has_started_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionFalse00TrueInformationLowTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.The_SQL_Server_Service_Broker_or_Database_Mirroring_transport_is_disabled_or_not_configured_5_RuleMSSQL on Linux: The SQL Server Service Broker or Database Mirroring transport is disabled or not configuredThe 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.Linux.EventRule.DBEngine.The_SQL_Server_Service_Broker_or_Database_Mirroring_transport_is_disabled_or_not_configured_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionFalse00TrueErrorHighTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.The_user_is_not_allowed_to_truncate_the_system_table_1_5_RuleMSSQL on Linux: The user is not allowed to truncate the system tableThe TRUNCATE TABLE statement cannot be issued for a system table, even if the allow updates configuration option is enabled.Microsoft.SQLServer.Linux.EventRule.DBEngine.The_user_is_not_allowed_to_truncate_the_system_table_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Transaction_was_deadlocked_on_resources_with_another_process_and_has_been_chosen_as_the_deadlock_victim._Rerun_the_transaction_1_5_RuleMSSQL on Linux: Transaction was deadlocked on resources with another process and has been chosen as the deadlock victim. Rerun the transactionThis 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.Linux.EventRule.DBEngine.Transaction_was_deadlocked_on_resources_with_another_process_and_has_been_chosen_as_the_deadlock_victim._Rerun_the_transaction_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Unexpected_end_of_file_while_reading_beginning_of_backup_set_1_5_RuleMSSQL on Linux: Unexpected end of file while reading beginning of backup setThe 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.Linux.EventRule.DBEngine.Unexpected_end_of_file_while_reading_beginning_of_backup_set_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.Unique_table_computation_failed_1_5_RuleMSSQL on Linux: Unique table computation failedUnique 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.Linux.EventRule.DBEngine.Unique_table_computation_failed_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.XML___Failed_to_instantiate_class._Make_sure_Msxml2.dll_exists_in_the_SQL_Server_installation_1_5_RuleMSSQL on Linux: XML: Failed to instantiate class. Make sure Msxml2.dll exists in the SQL Server installationThe 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.Linux.EventRule.DBEngine.XML___Failed_to_instantiate_class._Make_sure_Msxml2.dll_exists_in_the_SQL_Server_installation_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.XML___Failed_to_load_Msxml2.dll_1_5_RuleMSSQL on Linux: XML: Failed to load Msxml2.dllThe 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.Linux.EventRule.DBEngine.XML___Failed_to_load_Msxml2.dll_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.XML___FOR_XML_EXPLICIT_stack_overflow_occurred._Circular_parent_tag_relationships_are_not_allowed_1_5_RuleMSSQL on Linux: XML : FOR XML EXPLICIT stack overflow occurred. Circular parent tag relationships are not allowedThe 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.Linux.EventRule.DBEngine.XML___FOR_XML_EXPLICIT_stack_overflow_occurred._Circular_parent_tag_relationships_are_not_allowed_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.XML___Size_of_data_chunk_requested_from_the_stream_exceeds_allowed_limit_5_RuleMSSQL on Linux: XML : Size of data chunk requested from the stream exceeds allowed limitSQL Server received an XML document that exceeds the allowed limit.Microsoft.SQLServer.Linux.EventRule.DBEngine.XML___Size_of_data_chunk_requested_from_the_stream_exceeds_allowed_limit_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.XML___XML_document_could_not_be_created_because_server_memory_is_low._Use_sp_xml_removedocument_to_release_XML_documents_1_5_RuleMSSQL on Linux: XML : XML document could not be created because server memory is low. Use sp_xml_removedocument to release XML documentsWhen 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.Linux.EventRule.DBEngine.XML___XML_document_could_not_be_created_because_server_memory_is_low._Use_sp_xml_removedocument_to_release_XML_documents_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.XML___XML_error_1_5_RuleMSSQL on Linux: XML : XML errorThis 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.Linux.EventRule.DBEngine.XML___XML_error_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueWarningNormalTrue
Microsoft.SQLServer.Linux.EventRule.DBEngine.XML___XML_parsing_error_1_5_RuleMSSQL on Linux: XML : XML parsing errorThis 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.Linux.EventRule.DBEngine.XML___XML_parsing_error_1_5_RuleMicrosoft.SQLServer.Linux.DBEngineEventCollectionTrue00TrueErrorNormalTrue
Microsoft.SQLServer.Linux.Rule.MonitoringPoolAlertCollection.MonitoringErrorMSSQL on Linux: Monitoring errorThe rule traces monitoring workflows errors and generates error alerts.Microsoft.SQLServer.Linux.Rule.MonitoringPoolAlertCollection.MonitoringErrorMicrosoft.SQLServer.Linux.MonitoringPoolAlertCollectionAlertTrue00TrueErrorNormalTrueOperations Manager
Microsoft.SQLServer.Linux.Rule.MonitoringPoolAlertCollection.MonitoringWarningMSSQL on Linux: Monitoring warningThe rule traces monitoring workflows warnings and generates warning alerts.Microsoft.SQLServer.Linux.Rule.MonitoringPoolAlertCollection.MonitoringWarningMicrosoft.SQLServer.Linux.MonitoringPoolAlertCollectionAlertTrue00TrueWarningNormalTrueOperations Manager