Automate alerts for database blockings.

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » SQL Server Newbies » Automate alerts for database blockings.

Automate alerts for database blockings.

Rate Topic

Display Mode

Topic Options

Author

Message

marygrace_laurente23

Posted Sunday, September 02, 2012 8:30 PM

SSC Rookie

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 7:50 PM
Points: 27, Visits: 122

Hi Everyone,

Just want to ask if anyone have "script" or jobs that will automatically check database blocking. I want to automate this kind of scenario and also create an email alert if there's database blocking.

This will be a big help to me.

Thanks in advance guys :)

Post #1353312

rhythmk

Posted Sunday, September 02, 2012 10:49 PM

Old Hand

Group: General Forum Members
Last Login: Saturday, November 10, 2012 9:30 AM
Points: 388, Visits: 603

marygrace_laurente23 (9/2/2012)

Did you try out something so far ?
Please let us know if have any issue in your approach.

--rhythmk
------------------------------------------------------------------
To post your question use below link

http://www.sqlservercentral.com/articles/Best+Practices/61537/
Smile

Post #1353332

dwain.c

Posted Sunday, September 02, 2012 11:15 PM

SSCrazy

Group: General Forum Members
Last Login: Yesterday @ 12:42 AM
Points: 2,338, Visits: 3,158

Blocking is a pretty normal activity as the database establishes locks to allow some queries to complete before beginning others. I don't think you really want to get an email in those instances, because in a high volume application you'll get tons of emails!

SELECT * FROM sys.sysprocesses WHERE blocked <> 0

The above query identifies blocked processes. It would probably be better to dump all of them into a log table and then analyze them at periodic intervals.

This link may help: http://blogs.msdn.com/b/nikhilsi/archive/2008/07/13/how-to-identify-blocked-sql-processes-quickly.aspx

No loops! No CURSORs! No RBAR! Hoo-uh!

INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?

Need to UNPIVOT? Why not CROSS APPLY VALUES instead?
Since random numbers are too important to be left to chance, let's generate some!
Are you too recursively challenged?
Splitting strings based on patterns can be fast!

Post #1353336

« Prev Topic | Next Topic »

Permissions