August 15, 2003 at 8:12 am
One of my application admins for a COTS package thinks we have a locking problem.
What is the best way to log the locking in SQL Server so that it can later be compared with logs created by a COTS package?
Edited by - robinhc on 08/15/2003 08:12:16 AM
Edited by - robinhc on 08/15/2003 08:12:57 AM
August 15, 2003 at 11:50 am
Currently we are having a problem with blocks, so, we created a holding table and populated that table with what database, user, command, blocking spid, blockde spid, database id, wait time etc. Then we created a scheduled task and started populating the table every five seconds. You could do the same for locking info by using the syslocks table.
Work like you don't need the money.
Love like you've never been hurt.
And Dance like no one is watching.
Work like you don't need the money.
Love like you've never been hurt.
And Dance like no one is watching.
August 15, 2003 at 3:12 pm
You could just pipe a sp_lock to a file every N period of time.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply