Beginning with SQL Server 2005, the server reports the duration of an event in microseconds (one millionth, or 10-6, of a second) and the amount of CPU time used by the event in milliseconds (one thousandth, or 10-3, of a second). In SQL Server 2000, the server reported both duration and CPU time in milliseconds. 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. - Microsoft Books Online
This is just a helpful tip so you don't waste time following a non-issue... :-)
Hey, I just came across your blog and will be following... I've been doing BI work for a few years and just picked up a couple of great tips in the last 10 minutes of reading your blog. First, the ability to insert multiple records at once, separating them by commas... how did I not know that!!! And the fix for the SSRS report viewer in Chrome/Firefox... I'll be trying that out tomorrow... but I'm not clear on which version of SSRS you were using so I don't know if it will work for me (I'm using SQL Server 2008).
Anyway, just wanted to a drop you a note and say thanks, and I hope you keep posting!
Hey! Thanks for the feedback!! I am glad this is helping people!
The Chrome/Firefox fix works in 2008 r2, not sure about any other version...
I have 4 posts almost ready to go, so look for them in the coming weeks.
Post a Comment