Post reply

SQL Profile

  • April 20, 2009 at 2:20 pm

    #133070

    For some reason when I sat sql profile, click start and all errors should go to the table, when I close the file the trace stops why is that? Do I need to keep it open the profiler all the time?

  • April 20, 2009 at 2:31 pm

    #981045

    If you're running a profile trace from SQL profiler, it's the client application that's receiving the trace from SQL and writing it to a table. Hence if you close profiler, the trace is stopped

    Are you aware that tracing via SQL profiler to a table is the most intensive way of running a trace and puts the most extra load on the server being traced? I've seen that bring down a server before.

    Rather use a server-side trace, write the trace to a file and then you can process the file after the trace has completed.

    http://www.simple-talk.com/sql/performance/finding-the-causes-of-poor-performance-in-sql-server,-part-1/

    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

  • April 21, 2009 at 12:30 pm

    #981695

    Thank you

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

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