September 21, 2008 at 9:52 pm
Hello,
Does hardware bottleneck can result in deadlock issue. I often see CPU spikes as well as Deadlocks in one my SQL server. So, just wondering if there is any relationship between them.
Thanks
September 22, 2008 at 1:29 am
Typically deadlocks are the result of poorly written code or poor indexing, but then so is bad performance in general.
Are the deadlocks recurring? If so, turn traceflag 1222 on (DBCC TRACEON (1222,-1)) and the deadlock graph will be written to the error log. From that you can see what processes were involved in the deadlock, what they were running at the time and what resources the deadlock occurred over.
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
September 22, 2008 at 7:46 am
GilaMonster (9/22/2008)
Typically deadlocks are the result of poorly written code or poor indexing, but then so is bad performance in general.Are the deadlocks recurring? If so, turn traceflag 1222 on (DBCC TRACEON (1222,-1)) and the deadlock graph will be written to the error log. From that you can see what processes were involved in the deadlock, what they were running at the time and what resources the deadlock occurred over.
I agree it's primarily a code problem. A bottleneck can expose the problem by causing resources to held longer than normal. In that case, the bottleneck could have been lucky. However, fixing the bottleneck would only reduce the likelihood of hitting the deadlock. It can't eliminate them. The earlier you fix the cause of the deadlocks, the better off you'll be. Otherwise, you're just postponing it, and you may not have the flexibility to deal with it when it becomes painful again.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply