Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Monitoring Blocks Expand / Collapse
Author
Message
Posted Thursday, February 3, 2005 2:16 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: 2 days ago @ 12:49 PM
Points: 138, Visits: 270
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/lPeysakhovich/monitoringblocks.asp


Post #159514
Posted Thursday, February 10, 2005 1:09 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, July 26, 2005 6:59 AM
Points: 2, Visits: 1
aba_lockinfo stored procedure also does its job well
Post #160746
Posted Thursday, February 10, 2005 8:42 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: 2 days ago @ 12:49 PM
Points: 138, Visits: 270
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.


Post #160841
Posted Monday, October 17, 2005 8:52 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, May 2, 2013 8:14 AM
Points: 8, Visits: 69
I have never heared of the KILL command causing a corrupt database; has anyone seen or heard of this happening?
Post #229376
Posted Thursday, January 4, 2007 4:40 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, July 28, 2014 10:42 AM
Points: 253, Visits: 540
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?
Post #334530
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse