Deadlock blues

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?
ThanksWe 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