When running profiler I am seeing strange duration times on some of
the processes. I have seen large numbers before on a logout, but this
is on stored procedure exectution times. It shows up about every 30
lines or so. The value is in the trillions, so it can not be
correct. The values always start with the same numbers only the last
2 or 3 numbers vary. Example: 18446744073709478. Anyone seen this
before?
Denny Cherry - 17 Jul 2008 18:15 GMT
I have seen that before. Unfortunately I was unable to find a fix. My
best guess is that it's either a calculation error in the code which
produces the trace, or the command is running so quickly that SQL
can't come up with an actual run time for it. (My best guess is the
first one.)
I haven't seen the problem in a while, but I'm currently running the
SQL 2008 GUI on my workstation.
Denny
>When running profiler I am seeing strange duration times on some of
>the processes. I have seen large numbers before on a logout, but this
[quoted text clipped - 3 lines]
>2 or 3 numbers vary. Example: 18446744073709478. Anyone seen this
>before?
Andrew J. Kelly - 17 Jul 2008 20:55 GMT
I have seen issues similar to that in the past and a reboot fixed it so we
never found out the cause. The Logout is to be expected as that is the
cumulative time since it first logged in.

Signature
Andrew J. Kelly SQL MVP
Solid Quality Mentors
> When running profiler I am seeing strange duration times on some of
> the processes. I have seen large numbers before on a logout, but this
[quoted text clipped - 3 lines]
> 2 or 3 numbers vary. Example: 18446744073709478. Anyone seen this
> before?
Linchi Shea - 18 Jul 2008 01:36 GMT
I wonder if this has anything to do with the cpu time drift. Do you see any
messages such as "The time stamp counter of CPU on scheduler id 2 is not
synchronized with other CPUs" in the errorlog?
Linchi
> When running profiler I am seeing strange duration times on some of
> the processes. I have seen large numbers before on a logout, but this
[quoted text clipped - 3 lines]
> 2 or 3 numbers vary. Example: 18446744073709478. Anyone seen this
> before?
Anand - 30 Jul 2008 15:32 GMT
May not answer your question directly, but I recently discovered that SQL
Server 2005 reports duration in microseconds (as opposed to milliseconds in
previous versions), but Profiler still shows it in milliseconds. This can
get confusing because when saved to a file or a table, you will start much
larger numbers than when viewing it through Profiler.
I have never seen Duration in trillions though - looks like some proc of
your requires a real tuning job :-)
Anand
> I wonder if this has anything to do with the cpu time drift. Do you see
> any
[quoted text clipped - 10 lines]
>> 2 or 3 numbers vary. Example: 18446744073709478. Anyone seen this
>> before?