Monitoring Blocks

  • Leo Peysakhovich

    Hall of Fame

    Points: 3880

    Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/lPeysakhovich/monitoringblocks.asp

  • Andriy Lishchynskyy

    SSC Rookie

    Points: 32

    aba_lockinfo stored procedure also does its job well

  • Leo Peysakhovich

    Hall of Fame

    Points: 3880

    There are many ways and many people develop similar processes. I did outlined some of aspects. That's it. sp_who proc is working fine. Who need sp_who2? But it is exists as well.

  • Bret Mitchell

    SSC Enthusiast

    Points: 174

    I have never heared of the KILL command causing a corrupt database; has anyone seen or heard of this happening?

  • Sam Greene

    SSCertifiable

    Points: 5252

    Is P_MON_CONNECTIONS intended to be run when investigating blocks identified by the previous procs?  first I was thinking it was the main proc which fired off the sp_who logging proc, since runs a job passed as a parameter, but then i see the hostname parameter which makes me think that first you identify a host which is blocking and then run this proc on that hostname.  Is this correct?

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply