April 28, 2004 at 12:42 pm
I've set the trace 1204 on a SQL Server 2000 SP3a server. I know it is active because I have deadlocks being written to the SQL Server Log.
When I execute dbcc tracestatus(-1). I get the message
Trace option(s) not enabled for this connection. Use 'DBCC TRACEON()'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
So execute dbcc traceon(1204) and then dbcc tracestatus(-1) and it lists 1204 as being active. When I exit query analyzer and start it up again and execute dbcc tracestatus(-1) it gives the same not found message.
Is this a bug? Is anyone else having the same problem?
David Bird
May 3, 2004 at 8:00 am
This was removed by the editor as SPAM
June 1, 2004 at 2:39 pm
I found the answer I needed.
The traceon command needed the value -1 added to it
To set trace
dbcc traceon (1204, 3605, -1)
To query trace through another connection
dbcc tracestatus(-1)
David Bird
March 29, 2005 at 9:18 pm
Hi David,
I am having the same problem and noticed your post.
When u use dbcc traceon (1204,3605,-1),
what is the 3605??? just another traceflag ?? does the -1 set it permanently for other connections?
Thanks
Lyn
March 30, 2005 at 6:42 am
3605 Sends trace output to error log.
For all trace values see http://www.extremeexperts.com/SQL/Articles/DBCCTraceFlags.aspx
The trace seems to be permanent until the instance is stopped/started.
To keep it permanently, these trace flags need to be added to the Instance Start up parameters.
-T1204
-T3605
David Bird
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply