Why SQL Server DATETIME type saves time in ticks of 1/300 of a sec? -
The SQLServer datetime format is stored as 8 bytes, where 1 January 1900 and the second after the first four There is a number of four bytes, the number of bytes is very high by midnight and the tick is 1/300 of the second.
I wonder why this is? Where is it that came from 1/300? There should be some historical reasons for this.
Yes, there is a historical reason: Unix!
For details, who read it by Celco.
This is the information you are looking for:
Temporal data in T-SQL is a Unix system clock tick and round errors With only three decimal seconds, the new ANSI / ISO data types can go up to seven decimal seconds, a correct date and time data type. Since they are new, most of the programmers are not using them.
Comments
Post a Comment