DBCC TRACEON (1204)

[andreis]

Hi,
I ran DBCC TRACEON (1204) in order to catch deadlock info in the SQL 2000 error log, a deadlock was indicated by Performance monitor, but nothing showed up in the Error log. We need to find the source of the deadlocking, any ideas on that? Also, one web page suggested SQL Server Profiler's Create Trace Wizard to run the "Identify The Cause of a Deadlock" trace. Can't find on my Developer SQL 2000 Profiler anything but Index Tuning Wizard.
Thanks.
Andrei

 

[NoCoolHandle]

Buy Inside SQL Server by Kalen Delane.. THis is a great book and should help to solve many of your problmes..

An Excerpt..

To capture deadlock output..

The following is a fragment of the output from sqlservr.exe, which was started from the command line using –T1204. This example uses the conversion deadlock script that we used previously—issuing the same batch from two connections—to illustrate the output of trace flag 1204. To capture deadlock information, you must start SQL Server from a command prompt; the output of the trace flag will be displayed in the command window. If you're running a named instance of SQL Server 2000, you must be in the binn directory for that instance (such as \mssql$MyInstanceName\binn), and you must also supply the instance name with the -s parameter.

My memory of using the -t switch is that you need to keep the command prompt open to see the output. Check BOL.. It has been awhile.

Rob

She is still giving incorrect credit to someone else for some code I wrote, so I figure you can have some of hers as if I wrote it

 

[NoCoolHandle]

Oh yeah.. DBCC Traceon (1204) by itself won't output any good data, you need to specify where to send the output 3604 = client app, 3605 = log?

But that would be for a single connection, you really seem to need the sqlservr -T1204

Rob