BOL states incorrect return datatype for CURRENT_TIMESTAMP, GETDATE, GETUTCDATE - by John Paul Cook

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 779097 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 2/12/2013 8:11:44 PM
Access Restriction Public


Books Online incorrectly states that CURRENT_TIMESTAMP "Returns a datetime2(7) value that contains the date and time of the computer on which the instance of SQL Server is running. The time zone offset is not included." See for the error.

It appears that when the documentation was written, the "Higher-Precision System Date and Time Functions" was copied and pasted into "Lower-Precision System Date and Time Functions" without all of the necessary changes being made to the copied text.

If BOL is not incorrect, you need to reconcile how the "Return value" column does not agree with the text in the "Return data type" column of "Lower-Precision System Date and Time Functions".

Sign in to post a comment.
Posted by Microsoft on 2/28/2013 at 10:12 AM
Hi John,
Just a follow up to let you know the corrected topic has been published to MSDN.

Gail Erickson
SQL Server Documentation team
Posted by Microsoft on 2/13/2013 at 4:31 PM
Hi John,
Thanks for filing this Connect item. We'll get the topics updated as soon as possible.
Kind regards,
Gail Erickson
SQL Server Documentation Team