SQL Traces

  • I have discovered some traces that are consuming space on an old server running sql server 2000.

    I found them by running:

    SELECT * FROM ::fn_trace_getinfo(NULL)

    111

    12NULL

    135

    142014-07-01 09:37:17.000

    151

    211

    22NULL

    235

    242014-07-01 09:37:17.000

    251

    I am able to close/stop them, but they continue to come back...how do i stop them completely?? They consume about 10gb a month.

    Thanks

  • If they re-appear automaticly, they could be started by an SQL Agent job or perhaps by an application (like a monitoring application). You need to find out the process that starts the trace(s).

    In SQL2000 there is no default-trace like there is in SQL2005+, so the running traces are not required by SQL itself.

    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply