<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
Article Discussions
»
Article Discussions by Author
»
Discuss content posted by Marios...
»
Monitoring Database Blocking Through SCOM...
74 posts, Page 8 of 8
««
«
4
5
6
7
8
Monitoring Database Blocking Through SCOM 2007 Custom Rules and Alerts
Rate Topic
Display Mode
Topic Options
Author
Message
JKG
JKG
Posted Wednesday, August 31, 2011 12:43 AM
SSC-Addicted
Group: General Forum Members
Last Login: 2 days ago @ 4:20 PM
Points: 421,
Visits: 729
Great article - very helpful!!!
Post #1167904
Marios Philippopoulos
Marios Philippopoulos
Posted Thursday, September 01, 2011 8:02 AM
SSCommitted
Group: General Forum Members
Last Login: Tuesday, June 11, 2013 10:20 AM
Points: 1,825,
Visits: 3,483
JKG (8/31/2011)
Great article - very helpful!!!
Thank you :)
__________________________________________________________________________________
Turbocharge Your Database Maintenance With Service Broker: Part 1
Real-Time Tracking of Tempdb Utilization Through Reporting Services
Monitoring Database Blocking Through SCOM 2007 Custom Rules and Alerts
Preparing for the Unthinkable - a Disaster/Recovery Implementation
Post #1168682
krn045
krn045
Posted Monday, January 21, 2013 9:43 PM
Grasshopper
Group: General Forum Members
Last Login: Monday, January 21, 2013 9:35 PM
Points: 15,
Visits: 68
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.
Post #1409775
Marios Philippopoulos
Marios Philippopoulos
Posted Wednesday, February 06, 2013 6:37 PM
SSCommitted
Group: General Forum Members
Last Login: Tuesday, June 11, 2013 10:20 AM
Points: 1,825,
Visits: 3,483
krn045 (1/21/2013)
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.
Sometimes the blocking session is not doing anything, and there is therefore not much info on it (that info would be coming from sys.dm_exec_requests).
A good example of this would be a user-initiated session in which the user has opened a web page, and that has started a transaction that won't commit until the page is exited (code defect). In that scenario a SQL statement in the transaction could be blocking others indefinitely, even though there is no work being done.
__________________________________________________________________________________
Turbocharge Your Database Maintenance With Service Broker: Part 1
Real-Time Tracking of Tempdb Utilization Through Reporting Services
Monitoring Database Blocking Through SCOM 2007 Custom Rules and Alerts
Preparing for the Unthinkable - a Disaster/Recovery Implementation
Post #1416779
« Prev Topic
|
Next Topic »
74 posts, Page 8 of 8
««
«
4
5
6
7
8
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
