December 15, 2006 at 9:09 am
I am seeing following error happening in multiple databases
Transaction (Process ID 877) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
Environment is a 2 node cluster with 8 GB memory on windows 2003. Since blocking is occuring in multiple databases I am not sure that the application is causing this error. We cannot find any issues with the environment either. Everything seems normal.
Any idea how to tackle this?
Thanks
December 15, 2006 at 1:04 pm
This is exactly caused by an application. Two processes are performing conflicting updates in different orders and causing a deadlock. The best thing to do is run Profiler and track activity and then examine the data to see which process is getting killed.
December 15, 2006 at 2:02 pm
Enable the trace flag 1204 to write the deadlock information to sql error log...
You may not get completed dead lock info in sql 2000 profiler.
http://www.sqlservercentral.com/columnists/skumar/tracingdeadlocks.asp
http://www.sql-server-performance.com/deadlocks.asp
MohammedU
Microsoft SQL Server MVP
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply