Deadlock in SQl 2000

Question

Deadlock in SQl 2000

Ole Halstensen

SSC Rookie

Points: 28
More actions
March 15, 2007 at 1:57 pm

#153480

I have som problems with lock on a tabel , I think its when the users use piovot from Excel
Is there any way I can find out whats making locks
or is it anyway I can disable use of Piovot for 1 or 2 days , just for testing
I have about 120 users on Sql in many country ,
Please open for any way to try to solve this problem

Ole H
pers-tek@online.no

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

mrpolecat SSCertifiable Points: 7014 More actions · Answer 1

Through enterprise manager you can view which process is blocking and view the properties of the process to see what it is and who is doing it.

Jeff Moden SSC Guru Points: 1004356 More actions · Answer 2

sp_lock

sp_who2

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Ken McKelvey SSCoach Points: 18843 More actions · Answer 3

Erland Sommarskog has some useful scripts at:

http://www.sommarskog.se/sqlutil/aba_lockinfo.html

CGSJohnson SSCertifiable Points: 7208 More actions · Answer 4

I'm also encountering a problem with blocking. The problem is that when I run DBCC Inputbuffer with the id of the process that is blocking, there are no results (I can't see what the last executed statement was). Any idea how to get at this? I'm assuming that it won't be in the profiler results either, if I run that, right? Thanks.

Chris