Server side trace

  • I started server side trace on one of my production sql servers and after moving server to another node of cluster trace stopped. Is there any way that i can start it automatic when nodes transfer again?

  • irena did you use sp_create_trace to make a trace, or did you use profiler?

    a trace created with sp_create_trace runs until it is explicitly stopped or, if it was created with a @STOPTIME parameters, until that datetime is reached...so if you created it, it should still be running.

    if you select * from sys.traces, you should see somethign like this:

    idstatuspath

    11c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\log_154.trc

    31NULL

    if the status is not = 1, then you might want to re-run the command, changing @traceidout to the integer of the traceid you find.

    exec sp_trace_setstatus @traceidout, 1 ---start trace

    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!

  • Your commands look like you have sql server 2005 and i have sql2000. My commands are

    select * from ::fn_trace_getinfo(3)

    312

    32W:\trace\STBTrace

    331

    34NULL

    351

    I run server side trace with script and it is making files of 1M and it was working just fine until we transferred from one node of the cluster to another and during that transfer trace stopped. Is this normal or not?

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

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