Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Performance trace Expand / Collapse
Author
Message
Posted Saturday, December 06, 2008 2:13 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Monday, December 01, 2008 8:01 AM
Points: 369, Visits: 77
Comments posted to this topic are about the item Performance trace
Post #615164
Posted Monday, December 08, 2008 1:24 PM


Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Wednesday, April 16, 2014 1:45 PM
Points: 770, Visits: 1,178

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


SQLServerNewbie

MCITP: Database Administrator SQL Server 2005
Post #615763
Posted Monday, December 08, 2008 10:00 PM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Thursday, March 20, 2014 7:32 AM
Points: 5,198, Visits: 1,368
A little tricky one but good one.


Post #615923
Posted Tuesday, December 09, 2008 8:16 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Tuesday, December 07, 2010 8:13 AM
Points: 436, Visits: 322
I was thinking in thousanths of a second. Isn't that what VB uses or am I just several zeros off everywhere?
Post #616197
Posted Tuesday, December 07, 2010 12:58 PM


SSCrazy Eights

SSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy Eights

Group: General Forum Members
Last Login: Today @ 7:47 AM
Points: 8,296, Visits: 8,750
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
Post #1031470
Posted Thursday, December 27, 2012 4:27 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Wednesday, November 13, 2013 10:04 AM
Points: 414, Visits: 73
Trace will show the duration in milliseconds. Correct answer should be third option. Please check it out
Post #1400556
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse