Step 1: read the wiki page John sent.
Step 2: Deadlocks take two resources to tango. You need to see what the
two resources in question are. Run a trace and filter for deadlocks and
lock escalations. That will give you some more information about ground
zero at the time of the error.
Are the
http://en.wikipedia.org/wiki/Deadlock
On Thu, Aug 27, 2009 at 8:46 AM, Chad Gray wrote:
>
> I occasionally see this error in an application I wrote.
>
> Transaction (Process ID 54) was deadlocked on lock | communication buffer
> resources with another process and has been chosen as the deadlock
Deadlocks are hard to trouble shoot..
don't overly use with select... i.e espcially.. when
doing Select MAX(ID) instead use.. following in the insert..
SELECT @@IDENTITY AS whateverFiledName;
set nocount off
also for updates and deletes.. try... WITH(ROWLOCK)
Ryan Duckworth wrote:
Unfortunately there is no silver bullet for the problem of
deadlocking...they are a fact of life in multi-user, real-time applications.
However, you can do some things to severely limit the chances of them
occurring, and for properly handling them when they do.
Deadlocks occurr when Process A lock
Use transactions and better the DB design (which is easier said than done!).
Have you tied it down to one particular SQL Block? Maybe a report or an SP
running a cursor?
N
-Original Message-
From: Ryan Duckworth [mailto:[EMAIL PROTECTED]
Sent: 20 October 2004 17:02
To: CF-Talk
Subjec
how are u writing the queries? via stored procedures? or cfquery? I'm
assuming you're already cflock correct?
~|
Purchase from House of Fusion, a Macromedia Authorized Affiliate and support the CF
community.
http://www.houseoffus
6 matches
Mail list logo
