June 8, 2005 at 8:48 am
Hi,
is it ok to keep the Profiler open, even though I am saving the trace to a file? I mean, will it not impact memory if the actiual profiler app has millions of rows?
I don't see the way to close the profiler and still collect the trace data.
Thanks
June 9, 2005 at 2:37 am
As far as I understand it (and this is not guaranteed to be spot on) but the server definitely takes additional load while the profiler is running however the size of the output file is of no consequence other than disk space.
If you want to run the trace without using Profiler to write the output to file without listing the messages you can script the trace and execute it through a Query Analyzer window.
June 9, 2005 at 7:49 am
makes sense, thanks
June 9, 2005 at 12:45 pm
If you want to reduce overhead on doing traces, look into using server-side traces, without the Profiler GUI. These call the sp_trace_% extended stored procedures. Ken Henderson has a useful implementation on p.602 of his "The Guru's Guide to SQL Server Stored Procedures, XML, and HTML". I've also seen various other implementations (google for them). Using server-side tracing, I'm able to trace more events and fields with less impact than using the Profiler GUI.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply