Note: This feature is not available for SQL Server Analysis Services 2000.
The Windows CPU alarm becomes active when the total CPU utilization of the server exceeds a threshold. Sustained high CPU utilization can adversely effect the performance of SQL Server and anything else using this server.
Note that since this is a Windows-based metric, it can include CPU that was consumed by non-SQL Server processes.
When this alarm is current, you should:
Look at the Sessions page on the Activity drilldown. Sort the Sessions grid by Last Command CPU Time to see which sessions are consuming the most CPU.
Consider upgrading to a faster CPU or adding processors to your server.