How to identify locked tables and how to release the locks?

One of the SPs in my database takes long time to execute. The same SP executes faster in another DB. My colleague suggests that the tables could be locked in my DB and I've to release the locks (in which the SP refers) from the tables. How to identify the issue is due to locks and how to release them?

Please do suggest. Thanks.
LVL 16
Easwaran ParamasivamAsked:
Who is Participating?
 
AndyAinscowConnect With a Mentor Freelance programmer / ConsultantCommented:
Are the tables (in the two different databases) the SP operate upon identical in structure ?  (An index in one table that isn't in the other can make a vast difference to the time an SP takes to complete).
0
 
Patrick BogersConnect With a Mentor Datacenter platform engineer LindowsCommented:
Hi

Look under management (right click) and select View locks by object.
0
 
Surendra NathConnect With a Mentor Technology LeadCommented:
you can use the sp_lock2 stored procedure to find out if there are any locks on the tables involved
if that stored procedure is not already there in your database then you can get it from here

http://support.microsoft.com/kb/255596

I suggest you also try to update the statistics once and see if it resolves the performance issue

sp_updateStats

the above statement will update the stats of all the tables involved...
0
 
Jacques Bourgeois (James Burger)Connect With a Mentor PresidentCommented:
Andy has the most common and easiest to fix problem with slow stored procedures: tables that are not indexed properly.

The difference of speed between 2 databases might be that the amount or the values of the joining and ordering fields are different from one database to another. The amount of traffic can also play a role.

If you find out that locks are the problem, be careful. Locks are usually there for a good reason: to prevent multiple writes to the same data from 2 different sources at the same time. Removing them to speed up things would create more important problems.

Is your application the only one that uses that database? If so review your code for the most common cause of locks: transactions. You might be starting transactions that you do not commit or rollback as soon as the operations are finished, so they are holding locks uselessly. You might also be using transactions in places where they are not needed.

If other applications use that database, try to see if the same thing could not happen in these too.
0
 
Easwaran ParamasivamAuthor Commented:
Thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.