Posted by Erland Sommarskog on 08/16/06 07:15

rawheiser (rawheiser@gmail.com) writes:
> It IS an insensitive cursor.

As I said, it was a shot in the dark.

> Looking thru DBArtisan I see the KeyLocks in its lock display window,
> and in SQL Spotlight I see the number of locks jump by 1000 or so every
> few seconds.

And it retains the locks?

> How can I monitor what procedure is locking what resource?

Maybe my aba_lockinfo can be of help? If your procedure releases the locks,
then you will have to get the right moment, but if it retains the locks
you will see what it is. You find aba_lockinfo at
http://www.sommarskog.se/sqlutil/aba_lockinfo.html.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

• Next in forum: Re: clustered vs. non clustered
• Prev in forum: Weird situation - Stored procedure executed twice
• Thread view: Re: After SP4, proc w. Cursor doesn't release keylocks

[Reply to this message]