Re: Duration values misreported in Profiler

Can you check what are your Power Options on that server (in Windows)? If it is anything else than 'Always On', it may be causing problems.

Time calculations for the duration value are done using the processor frequency as parameter. With power saving on, frequency changes to save energy and makes our calculations inaccurate. Also, when there is more than 1 processor, power savings is applied differently depending on the processor's workload and will cause the values to go out of sync between processors.

There were some fixes done in that area for SP2 that eliminated some class of problems, but not completely for situations like above.

Regards,
Maciek Sarnowicz

"dvc" <dvc@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:CE6CF146-1088-482E-9E77-9963FCCE85D4@xxxxxxxxxxxxxxxx
Running the trace again, it's continuing to misreport. For example,

StartTime: 2007-11-01 14:52:17.153
EndTime: 2007-11-01 14:52:17.170
Duration: 18446744073709539

It's pretty much arbitrary between stored procedures and times.. This is a
production box, so I'm not keen to reboot it to fix what may just be
curiosity, but I'll update this discussion as and when I have more
information.

dvc

"Andrew J. Kelly" wrote:

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
>>
>>


.

Relevant Pages

  • Re: Performance really poor if calling data from sql clients
    ... The power management is set to a mode that no power off for hard disk nor CPU ... Andrew J. Kelly SQL MVP ... profiler to see what is happening on the sql server end. ...
    (microsoft.public.sqlserver.clients)
  • Re: SBS Server keeps shutting down
    ... as we have had a few power cuts recently and the server kept chugging along. ... I have no idea what IPSec is ... multiple reboot mentioned above and some other troubleshooting steps ...
    (microsoft.public.windows.server.sbs)
  • RE: Outlook Express Connection Problem
    ... "Connection to the server has failed". ... button under Internet Connection Settings. ... Click Servers Tab; ... On the NIC properties click the Power Management Tab and Uncheck this box: ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: What is easier: to delegate or to use ACLs?
    ... Joe Richards Microsoft MVP Windows Server Directory Services ... >>The reason for the delegation model isn't political. ... >>so the team with the power isn't even really working it out, ... >>folder under a project share for a server will generally have at least two ...
    (microsoft.public.windows.server.active_directory)
  • Re: Building a low-power FreeBSD media server
    ... If by "low power" you mean low power consumption (as opposed to the ... memory per TB of storage. ... and your server will be anything but low power consumption. ... generated by high density arrays of disk drives installed in the case. ...
    (comp.unix.bsd.freebsd.misc)