Post reply

Trace Cannot be Stopped

  • February 18, 2008 at 11:23 am

    #119984

    I have an errant trace running on a server that is filling up the disk space. Using the SYSAdmin account, we have run both...

    --stop a trace

    sp_trace_setstatus @traceid = 1 , @status = 0

    --close and delete a trace

    sp_trace_setstatus @traceid = 1 , @status = 2

    ...and we get the following error...

    Msg 8189, Level 14, State 32, Procedure sp_trace_setstatus, Line 1

    You do not have permission to run 'SP_TRACE_SETSTATUS'.

    Anyone seen this before?

  • February 18, 2008 at 3:15 pm

    #779484

    Not sure about the permissions thing, but is this on SQL 2005? Because trace 1 is a default trace that SQL Server 2005 always runs and needs to be stopped via sp_configure.


    Scott Duncan

    MARCUS. Why dost thou laugh? It fits not with this hour.
    TITUS. Why, I have not another tear to shed;
    --Titus Andronicus, William Shakespeare

  • February 19, 2008 at 2:43 pm

    #779948

    I found the spot where this is set up.

    Thanks for the push in the right direction.

  • February 19, 2008 at 2:43 pm

    #779949

    I found the spot where this is set up.

    Thanks for the push in the right direction.

  • February 20, 2008 at 7:28 pm

    #780475

    I really would not disable the default trace if I were you. Think of it as SQL's "black box". The load it places on the server should be minimal.

    - Tim Ford, SQL Server MVPhttp://www.sqlcruise.comhttp://www.thesqlagentman.com http://www.linkedin.com/in/timothyford

  • February 21, 2008 at 8:12 am

    #780668

    The problem is that is takes 200 Megs each day of disk space. This seems excessive to me for a "default" service.

Viewing 6 posts - 1 through 5 (of 5 total)

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