Re: Duration values misreported in Profiler
- From: "Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx>
- Date: Thu, 1 Nov 2007 10:34:10 -0400
That is what I run as well and I have not noticed this behavior. It would be interesting to see if it can be repeated or even happens again.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"dvc" <dvc@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:3F356125-5D4F-4CBC-B7CF-3427206CF5EC@xxxxxxxxxxxxxxxx
The server is at 9.00.3054.00, so nothing unusual there, I would have thought.
"Andrew J. Kelly" wrote:
Exactly which rollups do you have? I have some minor hot fixes and have
never noticed this behavior.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"dvc" <dvc@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F34C874F-B9FE-468D-89F0-79E4B73C10C0@xxxxxxxxxxxxxxxx
> Profiler (this is SQL Server 2005 SP2 with rollups) is reporting some
> interesting duration values for stored procedure execution:
> StartTime: 2007-11-01 10:17:58.180.
> EndTime: 2007-11-01 10:17:58.180.
> Duration: 18446744073709532
>
> I wonder if anyone else has seen this, or is my server just doing a bit > of
> time travelling?
>
> Thank you.
>
> DVC
.
- Follow-Ups:
- References:
- Re: Duration values misreported in Profiler
- From: Andrew J. Kelly
- Re: Duration values misreported in Profiler
- Prev by Date: Re: Duration values misreported in Profiler
- Next by Date: Re: Duration values misreported in Profiler
- Previous by thread: Re: Duration values misreported in Profiler
- Next by thread: Re: Duration values misreported in Profiler
- Index(es):
Relevant Pages
|