Home
  •  

CPU Utilization (\%)

Microsoft.SQLServer.2016.DBEngine.CPUUsagePercentMonitor (UnitMonitor)

CPU Utilization (\%) for 2016 DB Engine

Knowledge Base article:

Summary

Provides a measure of how much time processors actually spend working on SQL Server’s process threads.

Causes

All allocated CPUs are busy by processing SQL Server tasks.

Resolutions

Evaluate why SQL Server is using a high percentage of CPU using performance monitor SQL Server counters and performance related DMVs such as sys.dm_exec_query_stats.

Troubleshooting Performance Problems in SQL Server 2016

http://go.microsoft.com/fwlink/?LinkId=789165

Create an Extended Events Session

http://go.microsoft.com/fwlink/?LinkId=799311

Overrideable Parameters

Name

Description

Default Value

Alert Priority

Defines Alert Priority.

Normal

Alert Severity

Defines Alert Severity.

Error

Cache Expiration Time

Specifies the maximum age of information from cache the workflow can use. May be omitted.

43200

Enabled

Enables or disables the workflow.

Yes

Generates Alerts

Defines whether the workflow generates an Alert.

Yes

Interval (seconds)

The recurring interval of time in seconds in which to run the workflow.

300

Number of samples

Indicates how many times a measured value should breach a threshold before the state is changed.

6

Synchronization Time

The synchronization time specified by using a 24-hour format. May be omitted.

00:18

Threshold

The collected value will be compared against this parameter.

95

Timeout (seconds)

Specifies the time the workflow is allowed to run before being closed and marked as failed.

200

Element properties:

TargetMicrosoft.SQLServer.2016.DBEngine
Parent MonitorSystem.Health.PerformanceState
CategoryPerformanceHealth
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.SQLServer.2016.DBEngine.CPUUsagePercent.MonitorType
RemotableTrue
AccessibilityPublic
Alert Message
MSSQL 2016: CPU Utilization (\%) is too high
CPU Utilization of SQL instance "{0}" on computer "{1}" is too high. See "Alert Context" tab for more details.
RunAsDefault

Source Code:

<UnitMonitor ID="Microsoft.SQLServer.2016.DBEngine.CPUUsagePercentMonitor" Accessibility="Public" Enabled="true" Target="SQL2016Core!Microsoft.SQLServer.2016.DBEngine" ParentMonitorID="SystemHealth!System.Health.PerformanceState" Remotable="true" Priority="Normal" TypeID="Microsoft.SQLServer.2016.DBEngine.CPUUsagePercent.MonitorType" ConfirmDelivery="false">

  <Category>PerformanceHealth</Category>

  <AlertSettings AlertMessage="Microsoft.SQLServer.2016.DBEngine.CPUUsagePercentMonitor.AlertMessage">

    <AlertOnState>Error</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>Error</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.ServerRole"]/InstanceName$</AlertParameter1>

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

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="Normal" MonitorTypeStateID="Normal" HealthState="Success"/>

    <OperationalState ID="Error" MonitorTypeStateID="Error" HealthState="Error"/>

  </OperationalStates>

  <Configuration>

    <IntervalSeconds>300</IntervalSeconds>

    <TimeoutSeconds>200</TimeoutSeconds>

    <Threshold>95</Threshold>

    <NumSamples>6</NumSamples>

    <SyncTime/>

    <CacheExpirationTime>43200</CacheExpirationTime>

  </Configuration>

</UnitMonitor>