Post reply

Running DB trace on live server

  • March 24, 2011 at 12:29 am

    #236726

    Hello people

    I want to capture some trace results for only 1 stored proc to see all its different params

    I captured a light trace like textdate, database name etc filtered for only that SP but after starting the trace on our live DB server the CPU spiked to 95% and all our service was down.

    I was monitoring the CPU on [server] and I have hitted stop button as soon as the high CPU was noticed, which was less than 2 mins after I started. However, it took time for the trace to actually stop while it only stop until it finished capturing the lines in the cache.

    Can you help me how to stop the trace instantly. or is there any other best way to capture the SPs with different params.

    Thankx

  • March 24, 2011 at 2:05 am

    #1302819

    I assume (from the mention of a stop button) that you were using the Profiler GUI. Don't. Use a server-side trace rather.

    http://qa.sqlservercentral.com/stairway/72363/

    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

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

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

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