June 28, 2011 at 3:15 am
Hi All,
We have very odd issue that around 3AM to 4AM the CPU utilization of the server goes to 100 %. I canot see anything causing this from SQL side. None other than SQL is also working on the machine too.
The second call was SCOM set on the server. Could some one shred some light on the CPU utilization when the SCOM triggers the update request.(http://blogs.technet.com/b/operationsmgr/archive/2011/02/03/fix-sql-server-hits-100-cpu-utilization-when-there-are-configuration-update-requests-in-scom-2007.aspx)
How can I see the schedule of the trigger and how can i Stop the same.
Appreciate your early response.
June 28, 2011 at 4:25 am
You need to go into SCOM itself and look at how it's collecting data from that server. From the sounds of things you have it configured to only pull data once a day. Depending on how much data is being collected, it has to work very hard to put all that together. If you pull your data more often, the load will be distributed across the entire day.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply