Re: SQL Profiler / DBCC Traceon (1204)
From: Russell Fields (RussellFields_at_NoMailPlease.Com)
Date: 03/01/04
- Next message: Randy Hersom: "Detecting whether a trace is running"
- Previous message: Sebastian K. Zaklada: "Re: SQL 2000 Queries are 3 times Slower on DUAL XEON vs DUAL PIII"
- In reply to: Dan: "SQL Profiler / DBCC Traceon (1204)"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 1 Mar 2004 15:05:07 -0500
Dan,
No. That would already be too late.
However, you could have a SQL Trace running (the server side of what SQL
Profiler displays) that traces ONLY deadlocks. Then, when one arose you
could get the info. Some small overhead on your server, but the 1204 trace
also adds some small overhead. (IIRC)
Russell Fields
"Dan" <anonymous@discussions.microsoft.com> wrote in message
news:4a9201c3ffc0$ee960a40$a501280a@phx.gbl...
>
> Presently I have my SQL Server set with DBCC Traceon (1204)
> to collect deadlock information. I would like to collect
> detail information on each deadlock. Is there away to
> have SQL Profiler start on a deadlock and collect detail
> information?
>
> Thank You,
>
> Dan
- Next message: Randy Hersom: "Detecting whether a trace is running"
- Previous message: Sebastian K. Zaklada: "Re: SQL 2000 Queries are 3 times Slower on DUAL XEON vs DUAL PIII"
- In reply to: Dan: "SQL Profiler / DBCC Traceon (1204)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
