January 12, 2006 at 6:16 am
Getting deadlocks on our sql 2000 server..
Apparently SQL svr has a limitation about row level locking, causing these deadlocks…That is, when 2 folks are updating the same row of data,,, a deadlock occurs…
Microsoft OLE DB Provider for ODBC Drivers | (0x80004005) | [Microsoft][ODBC SQL Server Driver][SQL Server]Transaction (Process ID 102) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. |
January 12, 2006 at 7:29 am
The deadlock is not caused by 2 processes updating the same row. A deadlock (in its most common form) is caused by 2 processes that are updating seperate resources and then require the same resource that the other of the processes has locked. Process A is waiting for process B to release its resource and vice versa.
Anyway, that aside. To get a better idea of what caused the deadlock, check out the SQL Server error log.
You'll need to turn on traces 1204 and 3605 to capture this information in the error log.
DBCC TRACEON (1204)
go
DBCC TRACEON (3605)
That will get you further than where you are now at least. Without that information though there is not much more you can do troubleshoot, unless you have a good idea of what procedures caused the deadlock.
Hope that helps.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply