Re: How to diagnose a deadly embrace
- From: "John King" <John.King@xxxxxxxxxxxxxxxx>
- Date: Wed, 29 Jun 2005 19:01:07 -0400
You can start SQL Server Profiler to trace which table is causing the lock.
John King
http://www.agileinfollc.com
"Mark Butler" <mredhat_nospam@xxxxxxxxx> wrote in message
news:eYpyqXLfFHA.1284@xxxxxxxxxxxxxxxxxxxxxxx
>I have an application which is running on 40 active workstations. I am
>encountering lock outs many times a day. When I run the stored procedure
>"sp_who2" I can see the spids that are blocked and by which other spid.
>
> If I "kill xx" where xx is the head of the blocking chain the system frees
> up. When doing the "sp_who2" I see a command column which only shows the
> start of a command like "insert", 'update", "select" or "AWAITING
> COMMAND". Is there a way to see the whole command to isolate which
> table(s) are causing the problem?
>
> Are there other tools to help me out?
>
> Desparately in need of help...
> Mark
>
.
- References:
- How to diagnose a deadly embrace
- From: Mark Butler
- How to diagnose a deadly embrace
- Prev by Date: Re: Enterprise Manager field > 900 chars not displaying post SP4
- Next by Date: Re: A good TSQL editor/debugger
- Previous by thread: Re: How to diagnose a deadly embrace
- Next by thread: SQL 2005 Profiler against SQL 2000 DBs?
- Index(es):
Relevant Pages
|
