December 20, 2007 at 7:20 pm
Hi,
In our production server, the deadlock happening frequently. Is anyone can help on how to troubleshoot and identify the deadlock and how to solve it? Thanks.
December 20, 2007 at 11:28 pm
Enable traceflag 1204. That will write the deadlock graphs into the SQL error log. With the info in the graph, you should be able to locate the cause of the deadlock and rectify the code.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 15, 2008 at 10:52 am
Hi,
Check out the below link on how to resolve Dead-lock things.
http://www.code-magazine.com/Article.aspx?quickid=0309101
Thanks -- Vj
February 28, 2008 at 10:51 pm
yes gailshaw is correct ,but i like to add that before rectifying your code just understand one thing that there are two kinds of deadlock ,namely cycle deadlock and conversion deadlock be careful while dealing with conversion deadlock because it is not easy to
February 28, 2008 at 11:31 pm
Hi
You can also use the activity monitor under management in SSMS. Here you can add filters including "blocking "filters to see the processes that are causing the blocking in your database.
"Keep Trying"
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply