Posted by rawheiser on 08/16/06 00:11

It IS an insensitive cursor.

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.

How can I monitor what procedure is locking what resource?

Other than injecting some debugging code into the procedures?

• Next in forum: Trying to do REALLY simple procedure and loop in SQL Server
• Prev in forum: Re: Views, UDFs
• Thread view: Re: After SP4, proc w. Cursor doesn't release keylocks

[Reply to this message]