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] additional commands, e-mail: mssqldba-[Email Address Removed]MS Sql Server LazyDBA home page