Error log procedures cause high CPU usage on host for SQL Server 2005 or 2008 (4228925)

Chat now with support

Return

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title

Error log procedures cause high CPU usage on host for SQL Server 2005 or 2008
Description

Experiencing high CPU usage on 2005 and 2008 SQL Server monitored instances due to a Spotlight script for the error log.
Cause

Spotlight uses a procedure sys.xp_readerrorlog with date parameters for Error Log to read only the last 5 minutes. But on older versions of SQL Server, it seems to be reading it all, which will cause high CPU and provide wrong data.
Resolution

WORKAROUND 1:
Disable the Error Log Scanning collection for the affected instances.
1. Select Configure | Scheduling option from the top of your screen.
2. Select the connection name from the drop-down list.
3. Disable both “Error Log Alarm" and "SQL Error Log Scan" collections.
4. Next, select Configure | Error Log Entries and select the connection name.
5. Enable 'Override the factory settings' and disable 'Enable error log scanning'.
SOLUTION 1:
The issue should be fixed by applying the latest fix packs of the related SQL Server versions.
Defect ID

DS-1563, SOSSE-7939

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title