|
|
Posted by Erland Sommarskog on 04/26/07 11:02
Matik (marzec@sauron.xo.pl) writes:
> So ... that means for me as fallow:
> The getdate() is not taking the current system time, only the buffered
> SQLServer system time.
I like to stress that is my own speculation of how the internals work.
> 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.
If my theory is correct, yes, this appears to be a correct conclusion.
> 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())
I would expect that CURRENT_TIMESTAMP to be just a synonym fot getdate(). It
would be funny if two equivalent functions are implemented in different
ways.
I also like to point out that this kind of behaviour that could be different
in different versions of SQL Server, or even in different service packs.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|