|
Posted by Dan Guzman on 10/01/32 11:17
As Erland mentioned, it seems you are experiencing blocking rather than
deadlocks. The deadlock trace flags are won't help in resolving a blocking
problem.
Long-term blocking is a symptom of long-running queries or transactions.
Blocking may be caused by poor application design or an indication that
tuning is needed. The key is to keep transactions and queries as short as
possible so that blocking locks are held only for short periods. It's a
good practice that one never waits on user response in an open transaction.
You can identify the resource blocking spid 55 with EXEC sp_lock 55. This
will show a status of WAIT for the resource in question. You can find the
name of an object by specifying the reported ObjId in the query SELECT
OBJECT_NAME(<ObjId>). Use DBCC INPUTBUFFER or fn_get_sql to determine the
SQL statements involved in the blocking.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"reddy via SQLMonster.com" <forum@SQLMonster.com> wrote in message
news:8e97e015504a44bf96d11d443d671bea@SQLMonster.com...
> Hi Dan
>
> I Created deadlock and opened new page and typed the command
> DBCC TRACEON (1205,3605,-1).
> I didn't see any deadlock message except
>
> (End deadlock search 9232 a deadlock was not found)
>
> but in enterprise manager showing spid 54 blocking and spid 55 blocked.
>
> even tried (1204).
>
> Can you please tell step by step how to see locking.
>
> i am using standard vresion
>
> Thanks
>
> --
> Message posted via http://www.sqlmonster.com
Navigation:
[Reply to this message]
|