April 12, 2007 at 8:29 am
Any suggestions on the best way to say trace definitions? I seem to always be recreating the same type of traces over and over. The trace templates seem a little clunky to me so I'm looking for a better way.
April 12, 2007 at 9:41 am
After you start your self-designed profiler, you may click File/Save As ...
April 12, 2007 at 10:58 am
Obviously, you can save the output hence the clunky remark.
The point of the question was to see if anyone has found a clever way to make the trace definition more usable (e.g. persist filter criteria).
April 12, 2007 at 3:48 pm
How can a trace definition be any more re-usable than saving off a template? Can you explain why this is clunky? I think we may be missing something here. Please expand on what you are trying to do.
April 12, 2007 at 8:05 pm
Fair question, by clunky I mean:
*server connection doesn't persist
*filters such as databaseid, duration doesn't persist.
*the template selection is just a drop down list. I can't save and organize templates on disk. It is all just one bucket
I'm decent with the tool but my use of it has been increasing. Maybe there are ways to do these things but I haven't found them.
April 13, 2007 at 8:44 am
Did you try to save your profiler in different format and modify it?
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply