Trace flag 1205 gives more information on deadlocks although having said
that its not a whole lot more than 1204. What I've done is run a series of
sp_lock + dbcc inputbuffer over a period of time and capture that into a
table and correlate with when the deadlock actually occurs.

-----Original Message-----
From: Schlieper, Paul [mailto:paul.[Email Address Removed]
Sent: Friday, November 28, 2003 12:48 PM
To: LazyDBA.com Discussion
Subject: RE: Deadlock


It is a rare system where deadlocks never occur.

You can use sp_lock, while a deadlock is occuring. Since SQL kills deadlocks
automatically, that might be a *very* short time.

You can also use trace flags 1204 and 3605 to have SQL Server put deadlock
information into the SQL Error logs.

You can read up on deadlocks in BOL.

P


-----Original Message-----
From: K.[Email Address Removed] [mailto:K.[Email Address Removed] Friday, November 28, 2003 5:37 AM
To: LazyDBA.com Discussion
Subject: Deadlock


Hi all

How to prevent Deadlock situations. How to find tables or transactions on
which Deadlock occurred. ?

Pls help me
Manoj kumar



*********************************************
This communication which may be confidential and privileged and the
views expressed herein may be personal and are not necessarily the
views of Coats Ltd. It is for the exclusive use of the intended
recipients(s). If you are not the intended recipient(s), please note that
any distribution, copying or use of this communication or the information
in it is strictly prohibited. If you have received this communication in
error, please notify us by email (Apps.[Email Address Removed] or telephone
our technical support helpdesk at Coats Ltd. +44 (0)20 8210 5100
(UK 0830h - 1800h, Mon-Fri, GMT) and then delete the e-mail and
any copies of it.
**********************************************


---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY Get today's
cartoon: http://www.LazyDBA.com To unsubscribe, e-mail:
mssqldba-[Email Address Removed] For additional commands, e-mail:
mssqldba-[Email Address Removed] REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY Get today's
cartoon: http://www.LazyDBA.com To unsubscribe, e-mail:
mssqldba-[Email Address Removed] For additional commands, e-mail:
mssqldba-[Email Address Removed]
This is a commercial communication from Commerzbank AG.

This communication is confidential and is intended only for the person to
whom it is addressed. If you are not that person you are not permitted to
make use of the information and you are requested to notify
<mailto:LONIB.[Email Address Removed] immediately that you have
received it and then destroy the copy in your possession.

Commerzbank AG may monitor outgoing and incoming e-mails. By replying to
this e-mail you consent to such monitoring. This e-mail message and any
attached files have been scanned for the presence of computer viruses.
However, you are advised that you open attachments at your own risk.

This email was sent either by Commerzbank AG, London Branch, or by
Commerzbank Securities, a division of Commerzbank. Commerzbank AG is a
limited liability company incorporated in the Federal Republic of Germany.
Registered Company Number in England BR001025. Our registered address in
the UK is 23 Austin Friars, London, EC2P 2JD. We are regulated by the
Financial Services Authority for the conduct of investment business in the
UK and we appear on the FSA register under number 124920.

**********************************************************************

MS Sql Server LazyDBA home page