Home Forums SQL Server 2008 SQL Server 2008 - General Unknown Traces - Keep restarting when stopped RE: Unknown Traces - Keep restarting when stopped

  • July 26, 2013 at 5:40 am

    #1636106

    note that the PATH variable is null?

    I'm sure that means because someone is actively using SQL Profiler to run the trace live; Profiler will instantly recreate the trace if it were stopped or dropped.

    I'm sure you've heard that that can have an impact when compared to a server side trace, so you need to get whoever needs that trace to script it out instead.

    run sp_who2 and see which machine is running any ProgramName starting with "SQL Server Profiler"

    mine says SQL Server Profiler - df2195da-7702-4117-9837-ecfb5ebd7239 for one i just started as the proof of concept.

    as far as i know, a scripted trace always has a file name; a profiler traces has a path that is null, because iut's being redirected to the applicaiton on a desktop , and not to a file on the server.

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!