|
|
Posted by David Portas on 09/26/06 20:29
Hugo Kornelis wrote:
>
> Getdate() (or, to use the ANSI standard name, CURRENT_TIMESTAMP) is
> accurate to 1/300th of a second. I've never seen it decrease. Apart from
> that, it is as accurate as the system clock of the server - if an admin
> sets the system clock three hours back, SQL Server will report from the
> past.
>
Just to split hairs over this a little: The maximum precision of the
value returned by GETDATE() is 1/300th of a second. That doesn't
necessarily mean it is *accurate* to within 1/300th of a second
compared to some other time measurement such as the system clock.
However, like Hugo, I have never heard of any issue where serial
executions of GETDATE() went negative. It's not difficult to verify
that the time returned by GETDATE() is within a fraction of a second of
the system clock value returned by other means.
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--
Navigation:
[Reply to this message]
|