Startup Parameter -T 1204

I am working with the RTM Standard Edition of SQL Server 2005 and Deadlock
trace output is not getting written to the error log.  I use the -T startup
parameter and specify -T1204; -T 3605.  I set the startup parameters using
the SQL Server 2005 Configuration Manager.  I then restart the SQL Server
service and create a deadlock.  The deadlock info. is not written to the
error log.

If I run the DBCC TRACEON (1204, 3605, -1) then the output appears in the
error log.

I also tried the low case ("-t") startup option and it did not work.  As a
last ditch effort, I set the -T 1222 startup parameter but once again the
trace output is not written to the error log.

This seems to be a bug.

Please help.

Thanks!

Chris

Are you 100% certain you specify the startup parameters for the correct inst
ance? I just added the
flag and I did indeed get a dump in the errorlog for my deadlock. Btw, Profi
ler has a nice graphical
deadlock viewer in 2005.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www. solidqualitylearning
.com/
Blog: http:// solidqualitylearning
.com/blogs/tibor/


"Cgal" < cgallelli@newsgroups
.nospam> wrote in message
news:%23mqLZ98OGHA.4052@TK2MSFTNGP15.phx.gbl...
>I am working with the RTM Standard Edition of SQL Server 2005 and Deadlock 
trace output is not
>getting written to the error log.  I use the -T startup parameter and speci
fy -T1204; -T 3605.  I
>set the startup parameters using the SQL Server 2005 Configuration Manager.
  I then restart the SQL
>Server service and create a deadlock.  The deadlock info. is not written to
 the error log.
>
> If I run the DBCC TRACEON (1204, 3605, -1) then the output appears in the 
error log.
>
> I also tried the low case ("-t") startup option and it did not work.  As a
 last ditch effort, I
> set the -T 1222 startup parameter but once again the trace output is not w
ritten to the error log.
>
> This seems to be a bug.
>
> Please help.
>
> Thanks!
>
> Chris
>