August 19, 2010 at 10:31 am
SQL 2000 does not have a default trace.
If trace files are been created it's because either C2 auditing is enabled or there's a custom trace running. First thing you should probably do is identify why there's a trace running, what its purpose is (and who created it). Once you know that you should be able to decide whether or not you can delete the trace files and/or stop the trace.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 19, 2010 at 12:37 pm
Hi Gail,
Thanks a lot for the reply.
Actually the server is a very old server and I'm not sure who created those trace files.
But One thing I can say is that the server is not that important.
That's why I have been assigned the task of removing (or stoping) those old trace files.
Thank You,
SQLRocks
August 19, 2010 at 2:02 pm
Hi Gail,
I found that these trace files are being created by C2 Auditing.
I disabled the trace with the help of this article.
http://www.sqlservercentral.com/articles/Monitoring/basicsofc2auditing/1547/
Thanks a lot for your help.
SQLRocks
Viewing 3 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply