Friday, February 4, 2011

Hotfix for SQL Server 2008 R2: 100% CPU utilization when there are configuration update requests in SCOM 2007 R2

The Operations Manager Support Team Blog posted an article describing a hotfix to solve the issue where the SQL server service may use 100% CPU when SCOM 2007 triggers configuration update requests.

Want to know more? Go here.

4 comments:

  1. AnonymousFebruary 4, 2011 at 7:38 PM

    Hi Marnix, please would you produce a guide on what is involved upgrading SCOM 2007 R2 using SQL 2008 to SQL 2008 R2? Your last one on SQL 2005 was very useful reading.

    ReplyDelete
  2. Marnix WolfFebruary 4, 2011 at 8:09 PM

    Hi Tim,
    Good question and as a matter of a fact it is already on my todo list for a few days now. First I have to finalize a series of postings about the health of SCOM, after that I will write a posting about that upgrade path.

    Cheers,
    Marnix

    ReplyDelete
  3. georgeFebruary 4, 2011 at 8:09 PM

    Do you know if this hotfix included in CU4? Or it has to be applied separately

    Thanks,
    George

    ReplyDelete
  4. Marnix WolfFebruary 4, 2011 at 8:53 PM

    Hi George,
    no this is a separate hotfix (a Cumulative Update actually) for SQL server 2008 R2. So it is not included with the CU for SCOM R2.

    Cheers,
    Marnix

    ReplyDelete

Note: Only a member of this blog may post a comment.