Home Forums Article Discussions Article Discussions by Author Discuss content posted by Marios Philippopoulos Monitoring Database Blocking Through SCOM 2007 Custom Rules and Alerts RE: Monitoring Database Blocking Through SCOM 2007 Custom Rules and Alerts

  • January 21, 2013 at 9:43 pm

    #1579430

    Hi..

    We are using SCOM 2007 to monitor SQL Server 2008 instances. I have checked the blocked sessions alert details in SCOM console as well as in OperationsManager database. I was not able to find the head_blocker (or lead blocker spid) details when more than 2 processes are involved in blocking.

    Eg: 1. SPID 87 is blocked SPID 85 (Details available, lead blocker is 85)

    2. SPID 87 is blocked by SPID 90

    SPID 90 is blocked by SPID 85 (Details available for SPID 87 and 90, here SPID 85 is blocker. There are no details available like hostname, logintime, cmd etc for SPID 85)

    I am not sure if this is the limitation in this product or something we should configure to capture the information when there are more than 2 spids involved in blocking.