Home
  •  

SQL User Connections Performance

Microsoft.SQLServer.2012.DBEngine.UserConnectionsBaselineMonitor (UnitMonitor)

This monitor analysis the user connections to the SQL database engine over time and calculates a baseline over the initial learning period.

Knowledge Base article:

概要

This monitor analysis the user connections to the SQL database engine over time and calculates a baseline over the initial learning period.A warning or error alert will be raised if the user connections figure moves outside the baseline that has been captured.

原因

An increase or decrease in the normal connections to the server could indicate a problem with SQL or some network infrastructure.

解決方法

Check for other alerts from SQL Server or specific databases on the server:

SQL アラート

Look at the key performance metrics for SQL that have been collected:

SQL パフォーマンス

Element properties:

TargetMicrosoft.SQLServer.2012.DBEngine
Parent MonitorSystem.Health.PerformanceState
CategoryPerformanceHealth
EnabledFalse
Alert GenerateTrue
Alert SeverityMatchMonitorHealth
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeSystem.Performance.TwoStateAboveBaseliningMonitorWithoutCompression
RemotableTrue
AccessibilityPublic
Alert Message
SQL User Connections Abnormal
SQL user connections for instance {0} running on computer {1} are abnormal
RunAsDefault

Source Code:

<UnitMonitor ID="Microsoft.SQLServer.2012.DBEngine.UserConnectionsBaselineMonitor" Accessibility="Public" Enabled="false" Target="SQL2012Core!Microsoft.SQLServer.2012.DBEngine" ParentMonitorID="SystemHealth!System.Health.PerformanceState" Remotable="true" Priority="Normal" TypeID="SystemPerf!System.Performance.TwoStateAboveBaseliningMonitorWithoutCompression" ConfirmDelivery="false">

  <Category>PerformanceHealth</Category>

  <AlertSettings AlertMessage="Microsoft.SQLServer.2012.DBEngine.UserConnectionsBaselineMonitor.AlertMessage">

    <AlertOnState>Warning</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>MatchMonitorHealth</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</AlertParameter1>

      <AlertParameter2>$Target/Property[Type="SQL!Microsoft.SQLServer.ServerRole"]/InstanceName$</AlertParameter2>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="BelowNormal" MonitorTypeStateID="Below" HealthState="Success"/>

    <OperationalState ID="AboveNormal" MonitorTypeStateID="Above" HealthState="Warning"/>

  </OperationalStates>

  <Configuration>

    <SignatureID>{D56436DB-41F0-4958-A8F0-9BC941674B4B}</SignatureID>

    <DataSourceSettings>

      <ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>

      <ObjectName>$Target/Property[Type="SQL!Microsoft.SQLServer.DBEngine"]/PerformanceCounterObject$:General Statistics</ObjectName>

      <CounterName>User Connections</CounterName>

      <InstanceName/>

      <AllInstances>false</AllInstances>

      <Frequency>300</Frequency>

    </DataSourceSettings>

    <LearningAndBaseliningSettings>

      <BusinessCycleLengthUnit>Week</BusinessCycleLengthUnit>

      <BusinessCycleLengthInGivenUnit>1</BusinessCycleLengthInGivenUnit>

      <LearningType>Continuous</LearningType>

      <Offset1>3</Offset1>

      <Offset2>3</Offset2>

      <Offset3>3</Offset3>

      <LearningRate>2.3333333333333335</LearningRate>

      <InitialNoAlertPeriodInBizCycles>1</InitialNoAlertPeriodInBizCycles>

      <OuterSensitivity>3.31</OuterSensitivity>

      <InnerSensitivity>2.81</InnerSensitivity>

    </LearningAndBaseliningSettings>

    <SignatureCollectionSettings>

      <DBUpdatePeriodInSeconds>300</DBUpdatePeriodInSeconds>

    </SignatureCollectionSettings>

  </Configuration>

</UnitMonitor>