|
|
Posted by Mike Reigler on 10/14/05 23:15
"byrocat" <bdealhoy@sympatico.ca> wrote in message
news:1129317166.975507.198020@f14g2000cwb.googlegroups.com...
> MIke, thanks for the reply. Two more quick questions:
>
> So, if we go through the exercise of defining the events that we wish
> to trace and generate the script file and then run the script file,
> this means that the settings are permanent (i.e., rebooting the server
> will not terminate the settings)?
>
> Can I also assume that the script can be used to set up can be used on
> other servers without changes?
>
> Thanks in advance!
>
The server side trace is not really permanent it just runs from when you
start it until it is stopped. I think rebooting the server would stop the
trace. You would have to use job scheduling to run the script on startup.
Also when you create the trace you specify how large the trace file can be
(the default is 5 MB). If you want to permanently capture the data you
would need to have a script scheduled to run periodically before the file
gets to the max size and copy the data from the trace file into a permanent
table and probably start a new trace.
Not exactly simple, but as long as your trace doesn't filter on specific
users etc. it should be portable to other servers.
All that being said, I've never run a trace permanently just used them to
troubleshoot a specific problem.
Navigation:
[Reply to this message]
|