Excessive Deadlocking, can anyone help me out?

[hih]

I'm getting this error:

"Error Executing Database Query. [Macromedia][SQLServer JDBC
Driver][SQLServer]Transaction (Process ID 63) was deadlocked on lock resources
with another process and has been chosen as the deadlock victim. Rerun the
transaction. "

About 25 times a day.

Our configuration is CF MX7 running on 2 servers clustered with a Big IP box.
One server runs MS SQL Server 2000 standard edition. The website is not getting
crazy traffic, maybe 2-3 simultaneous hits throughout the day.

What seems to happen is that the deadlock occurs when a page is running
updates to 4 different tables. I am not using cftransaction tags, could this be
the problem?

[Brian Hogue]

Are these 4 SQL Updates in your CF or in a Stored Procedure? If in CF, then
theoretically yes that could be the cause of your deadlock ... assuming that
you have a lot of other users updating at the same time.

-brian

"hih" <webforumsuser@macromedia.com> wrote in message
news:df1kk1$nqd$1@forums.macromedia.com...

> I'm getting this error:
>
> "Error Executing Database Query. [Macromedia][SQLServer JDBC
> Driver][SQLServer]Transaction (Process ID 63) was deadlocked on lock

resources

> with another process and has been chosen as the deadlock victim. Rerun the
> transaction. "
>
> About 25 times a day.
>
> Our configuration is CF MX7 running on 2 servers clustered with a Big IP

box.

> One server runs MS SQL Server 2000 standard edition. The website is not

getting

> crazy traffic, maybe 2-3 simultaneous hits throughout the day.
>
> What seems to happen is that the deadlock occurs when a page is running
> updates to 4 different tables. I am not using cftransaction tags, could

this be

> the problem?
>

[hih]

well the queries are not stored procedures, but i did a quick audit and it
seems that the 4 updates were all occuring against 1 data table in seperate
queries, very dumb i know, but the program is getting to be 5 years old and you
know how CF 4.5 code can get bad over time...