Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Transaction (Process ID 107) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. Expand / Collapse
Author
Message
Posted Wednesday, March 2, 2011 11:17 PM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, July 16, 2014 4:48 AM
Points: 279, Visits: 1,201
Dear All!

I have this problem in our one of module, Please let me know your suggestion to overcome this problem..

Transaction (Process ID 107) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.


Many Thanks!
S.saravanan
“I am a slow walker, but I never walk backwards-
Abraham Lincoln”
Post #1072352
Posted Wednesday, March 2, 2011 11:50 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 5:18 AM
Points: 42,417, Visits: 35,481
That's useless for fixing the problem.

Enable traceflag 1222. That will cause SQL to write the deadlock graph into the error log when a deadlock happens. Get the deadlock graph and post it, along with the definition of any tables and indexes referenced by the graph.

DBCC TRACEON (1222,-1)




Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1072358
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse