|
|
Posted by Matik on 04/26/07 10:00
First, thanks Erland for the answer!
> So you have an application that modifies the computer clock every
> second, and now you are asking why:
:) No ... of course, I'm not confused about the time changes :)
I'm expecting them ...
Confused for me, was this:
> > getdate() = '2007.04.25 10:59:55.000'
> > prm_recieved = '2007.04.25 10:00:00.000'
>
> getdate() does not always reflect you recently updated system time.
>
> I guess the answer is that there is not really reason that Windows and
> SQL Server would behave the way you may want it to in this very special
> scenario.
>
> One reason that getdate() apparently lags behind is that getdate() has
> a resolution of 3.33 ms which after all is quite a long time in a computer.
> Assuming that SQL Server reads the system clock every 3.33 ms, getdate()
> could seemingly lag behind your manipulated time.
Ok.
So ... that means for me as fallow:
The getdate() is not taking the current system time, only the buffered
SQLServer system time.
That means as well, that the time between changing system time,
writing into log (application) and calling procedure in DB, until this
position where the getdate() is called, MUST be shorter than a maximum
time of 3.33 ms.
Well, this is not I was thinking getdate() is doing:(
Is the current_timestamp function behaviour exactly in this way?
(probably yes, since in BOL says that this is the same as getdate())
Thank's Erland again for help.
Matik
Navigation:
[Reply to this message]
|