The Instance Cpu % alert notifies you when its configured condition is met on SQL Server instances so you can investigate and respond.
Mini DBA describes this alert as: % of the Cpu used by this Sql Server instance Sustained high usage may indicate poor T-SQL or index design Mini DBA evaluates this alert once a minute so changes are detected quickly. Because duration is used, Mini DBA can avoid treating a single short spike as a full incident when the condition clears quickly.
This alert highlights sustained CPU pressure. CPU saturation usually means queries, background tasks, or host contention are competing for scheduler time and can cause broad latency across the monitored workload.
Enable it once the instance has a normal workload baseline. It is especially useful on busy OLTP, reporting, and integration systems where resource pressure can quickly become user-visible.
Threshold meaning: % Cpu. Major threshold: 95 %. Minor threshold: 85 %. Comparison direction: over. Duration is used, so prefer requiring the condition to persist before paging people for transient spikes. For an over-threshold alert, decreasing a threshold makes that severity fire sooner; increasing it tolerates more load or pressure. Set the minor threshold as an early-warning level and the major threshold at the highest acceptable value for the service.
Find the top CPU queries, jobs, and host processes. Review recent deployments and plan changes, then tune indexes or queries, adjust schedules, reduce concurrency, or increase compute where the workload is legitimately larger than the instance can handle.
If this alert is noisy, check whether the workload naturally has short bursts. Raise the duration or threshold for expected batch windows, but keep a lower route for production systems where user-facing latency matters. Avoid simply disabling the alert until you know whether the noise is caused by threshold choice or by a real capacity trend.