Home > Archive > MS SQL Server > January 2006 > Deadlock blues









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Deadlock blues
Frank Rizzo

2006-01-30, 8:23 pm

I am trying to rewrite 2 stored procs that have been perpetually having
deadlock issues against each other. The current problem is that the
pieces of SQL that are involved in the deadlock are both in a
transaction. The contention is for a single table. Would moving the
offending piece of code in stored proc #1 out of transaction solve the
deadlocking issue?

Thanks
Andrew J. Kelly

2006-01-30, 8:23 pm

We would need to see the code. Moving a statement out of a tran may not
give you the desired results when it comes to data integrity. Most deadlocks
are caused by updating the tables in different orders.

--
Andrew J. Kelly SQL MVP


"Frank Rizzo" <none@none.com> wrote in message
news:%23HxuQteJGHA.208@tk2msftngp13.phx.gbl...
>I am trying to rewrite 2 stored procs that have been perpetually having
>deadlock issues against each other. The current problem is that the pieces
>of SQL that are involved in the deadlock are both in a transaction. The
>contention is for a single table. Would moving the offending piece of code
>in stored proc #1 out of transaction solve the deadlocking issue?
>
> Thanks



Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2008 droptable.com