January 13, 2007 at 6:52 am
I support a production machine in which we have been live now for over 10 months. Win2003/SQL2000. Over the past several days, nightly processes that have been running this entire production time on the exact same schedule have now been deadlocking.
System.Data.SqlClient.SqlException: Transaction (Process ID 250) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
This is a third party app for which I support so code changes for me wouldn't be possible. From a sql standpoint, is there anything I can do to monitor this situation? Setting changes?
January 13, 2007 at 9:48 pm
Enable trace flags 3605 and 1204 which will write the information to sql error log so that you can find what statement is causing the deadlocking...
DBCC TRACEON (3605,1204,-1)
Tips for Reducing SQL Server Deadlocks
http://www.sql-server-performance.com/deadlocks.asp
INF: Understanding and Resolving SQL Server 7.0 or 2000 Blocking Problems
http://support.microsoft.com/kb/224453
MohammedU
Microsoft SQL Server MVP
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply