http://support.microsoft.com/default.aspx?scid=kb;en-us;Q271509

Tells you to create a procedure and execute it via a batch job.....I
modified the procedure to only check for deadlocks, as the other waits
produced are 'normal' for my application.

I'm trying to create a batch script that will check the output file and
mail/page me if it is not empty; if anyone can do it faster, can you
post the results?

mary

-----Original Message-----
From: Thomas Henley [mailto:[Email Address Removed] Tuesday, July 16, 2002 10:52 AM
To: Mary Bahrami; [Email Address Removed] RE: Alert on Table locks


Why not share the URL for those who might be interested?

-----Original Message-----
From: Mary Bahrami [mailto:[Email Address Removed] Tuesday, July 16, 2002 1:48 PM
To: [Email Address Removed] RE: Alert on Table locks


Found it on MS site....

-----Original Message-----
From: Mary Bahrami
Sent: Monday, July 15, 2002 8:00 AM
To: [Email Address Removed] Alert on Table locks


I have a SS2000 application that does alot of table locking while
synching laptops to the database. I can't change the application, so I
need to identify when the laptop user pulls the plug while holding table
locks.

I tried setting up a canned alert based on 'Lock Wait Time(ms)', but the
counter just keeps growing as each table lock is set and released.
(also, we never shut the database down, so it never resets).

Does anyone have a good way of identifying true table locks that cause
problems? I can see that the sessions are 'blocking' for a while, but
don't know how to script it.

TIA,
mary

---------------------------------------------------------------------
To unsubscribe, e-mail: mssqldba-[Email Address Removed] additional commands, e-mail: mssqldba-[Email Address Removed] unsubscribe, e-mail: mssqldba-[Email Address Removed] additional commands, e-mail: mssqldba-[Email Address Removed]MS Sql Server LazyDBA home page