Posted by shiju on 08/01/07 03:22

On Jul 30, 1:17 pm, steven <sfuc...@verizon.net> wrote:
> I have a small database that I have been testing.
> I get an error about a transaction deadlock.
> The code is in stored procedures and I added transactions to the sp's
> but the error happened again.
>
> I wrapped the whole sp in just one transaction and I don't have any
> index on the tables.
>
> When I test just by running a program that sends 3 calls at a time it
> will get a deadlocked transaction as I send 6 or 9 at a time.
>
> I am not sure how it can have a deadlocked transaction after I used
> transactions(begin and commit) in the sp's.
>
> Steve

You didn't give much info. This might be due to non-availability of
index if you have an update or delete statement in the SP with a
filter. try creating an index on the filter column.

profile deadlock chain event and graph to figure out which object is
causing the event.

[Back to original message]