Re: DBCC TRACEON 3604
From: Ryan Stonecipher [MSFT] (ryanston_at_online.microsoft.com)
Date: 08/30/04
- Next message: Ryan Stonecipher [MSFT]: "Re: Database "Suspect""
- Previous message: Geoff N. Hiten: "Re: Automatic file grown"
- In reply to: Craig Brown: "DBCC TRACEON 3604"
- Next in thread: Craig Brown: "Re: DBCC TRACEON 3604"
- Reply: Craig Brown: "Re: DBCC TRACEON 3604"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 30 Aug 2004 09:28:12 -0700
A couple of things come to mind:
1. You can check the startup parameters in the registry of the SQL Server: HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/MSSQLServer/MSSQLServer/Parameters. It is possible that the trace flag is enabled there, and is turned on at startup.
2. Take a Profiler trace of the server to capture the hostname and/or application name of the client machine executing the DBCC TRACEON command.
Thanks,
Ryan Stonecipher
Microsoft SQL Server Storage Engine
"Craig Brown" <craig.brown@brucepower.com> wrote in message news:296301c48e8f$17398690$a501280a@phx.gbl...
We are operating 2 instances of SQLServer 2K SP3 which are
reporting that SYSTEM is executing DBCC TRACEON 3604.
I've checked on DBCC TRACEON which appears to be a
diagnostic tool and specifically 3604 which appears to
enable diagnostic information to be transfered to the
client. I don't believe that the client software
connecting to these instances are issuing the statement.
My question is how is this statement being executed and
how do I control it. I performed the DBCC
TRACEON/TRACEOFF statements in Query Analyzer and the
event viewer reports my account associated with the
event. The other events are associated with "SYSTEM".
Any help would be appreciated.
- Next message: Ryan Stonecipher [MSFT]: "Re: Database "Suspect""
- Previous message: Geoff N. Hiten: "Re: Automatic file grown"
- In reply to: Craig Brown: "DBCC TRACEON 3604"
- Next in thread: Craig Brown: "Re: DBCC TRACEON 3604"
- Reply: Craig Brown: "Re: DBCC TRACEON 3604"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|