Where Do I Want To Go Today? - Lossless Performance
-
Comments posted to this topic are about the content posted at http://qa.sqlservercentral.com/columnists/sjones/wheredoiwanttogotodaylosslessperformance.asp
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com -
Being someone who runs both Oracle and SQLServer, I couldn't help but smile at the comment "The current method of setting up profiler looks like something from Oracle, some cumbersome, archaic, gnome-like method for building a set of options for a trace. " The method for setting a trace in Oracle is either a simple ALTER statement, or a simple call to a system stored procedure with a maximum of 4 arguments.
The reason it is simple actually highlights to me the flaw of the profiler approach. In Oracle you decide the cope of your trace (connection or instance level) and the level of statistical detail required. The time for filtering comes when you come to *analyse* the trace file. I think this is right, it means that if you don't get your filter criteria quite right, or need to reanalyze the workload for different problems you don't need to resetup the trace.
Of course its possible that I'm just a gnome
Niall Litchfield
Senior DBA
http://www.niall.litchfield.dial.pipex.com
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply