December 6, 2008 at 2:13 pm
Comments posted to this topic are about the item Performance trace
December 8, 2008 at 1:24 pm
In SQL Server 2005, the SQL Server Profiler graphical user interface displays the Duration column in milliseconds by default, but when a trace is saved to either a file or a database table, the Duration column value is written in microseconds.
That is tricky, I was very certain I got it right (1061 seconds) because I have done too many durations tracking, IN GUI where I want things under 1000 (1 second).
Thanks for the tip
December 8, 2008 at 10:00 pm
A little tricky one but good one.
December 9, 2008 at 8:16 am
I was thinking in thousanths of a second. Isn't that what VB uses or am I just several zeros off everywhere?
December 7, 2010 at 12:58 pm
Either the answer is just plain wrong or the question is sloppily worded.
The appropriate BoL statement is (as quoted in the explanation)
In SQL Server 2005 and later, the SQL Server Profiler graphical user interface displays the Duration column in milliseconds by default, but when a trace is saved to either a file or a database table, the Duration column value is written in microseconds.
So if the trace is viewed in the profiler GUI the duration is shown in milliseconds and the answer given as "correct" is 3 orders of magnitude too small.
On the other hand, maybe the question meant that the trace was setup to write to a table, and the select referred to wasn't what was traced but was a select to read from that table. That's a very different question, and if that had been the question provided then the duration would be in microseconds and the answer provided would have been right.
Tom
December 27, 2012 at 4:27 am
Trace will show the duration in milliseconds. Correct answer should be third option. Please check it out
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply