Extended Events Durations - by Ola Hallengren

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 786158 Comments
Status Resolved Workarounds
Type Bug Repros 3
Opened 5/2/2013 2:10:49 PM
Access Restriction Public


The durations for some extended events are in milliseconds and some are in microseconds. It is not always documented.

Could I ask to have this made consistent to microseconds or at least clearly documented in the field descriptions.
Sign in to post a comment.
Posted by Ola Hallengren on 12/13/2017 at 11:42 AM
The description has been updated in sys.dm_xe_object_columns.description. It now says if it is milliseconds or microseconds.
Posted by JBrune on 12/13/2017 at 10:17 AM
Can we get an answer or an update on this?
Posted by LeptonJoe on 1/31/2017 at 2:09 PM
In what version is this fixed? Is it only 2016 that this has been corrected? What was the correction?
Was documentation added to show the units or did the units all get switched to the same precision?
If I look at the duration of wait_completed vs module_end, one is microseconds and the other is milliseconds.
Posted by Ranga1 on 1/4/2017 at 7:16 AM
how many of us really care about micro seconds ?? Does Microsoft even do some analysis as what the user needs are before they decide on something. Milli seconds is a good enough bar, just like we had in sql profiler. I want to ask MS if there are any connect item to change milli seconds to micro seconds? Please revert all micro seconds to milliseconds, lets see what is user friendly!
Posted by galapiat on 6/28/2016 at 12:42 AM
My god three years that this bug is open. Fix it dammit!

How can we be supposed to replace SQL Profiler with Extended Events when glaring bugs in Extended Events don't get fixed???
Posted by Microsoft on 4/15/2014 at 6:49 PM
We have reopened the DCR. We are planning to address it in the next release of the product.
Apologies for the confusion.

Posted by F. Dwarf on 2/28/2014 at 10:55 AM
If not fixed, could it be at least well documented?
Posted by Ola Hallengren on 11/6/2013 at 3:36 PM
Thank you for the answer. I think that it is very confusing for users (especially as it is not documented in the Field Descriptions for all events), and that you should try to get it fixed (it is wait_info and wait_info_external that should be changed from milliseconds to microseconds). I think that Microsoft has invested a lot of resources in Extended Events in the last 2 - 3 releases, and that it is important to fix issues that are reported to make it as easy as possible for users to go from Trace to Extended Events. Maybe it could be fixed in a service pack or a cumulative update package?
Posted by Microsoft on 11/6/2013 at 12:03 PM
Hi Ola,

Thanks for your feedback. Unfortunately we aren't able to include this fix as it doesn't meet our prioritization bar for the next release. If this is an urgent issue that is causing functional problems or causing significant issues using SQL Server, please let us know and we will re-consider.

Posted by Shawn Quillman on 8/29/2013 at 12:38 PM
There is also discrepancy within the same events between SQL Trace and extended events. For example, auto growth durations for SQL trace are reported in milliseconds, as documented at http://technet.microsoft.com/en-us/library/ms187491.aspx. However, XE auto growth duration is clearly reported in microseconds. I can't find a reference for XE autogrowth fields, though. I had to use the difference between StartTime and EndTime to confirm.