Search

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

Closed
as Fixed Help for as Fixed

2
1
Sign in
to vote
Type: Bug
ID: 779097
Opened: 2/12/2013 8:11:44 PM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
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 http://msdn.microsoft.com/en-us/library/ms186724.aspx 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".

Details (expand)

Product Language

English

Version

SQL Server 2012 - Enterprise Edition

Category

Documentation

Operating System

Not Applicable

Operating System Language

US English

Steps to Reproduce

1. Go to http://msdn.microsoft.com/en-us/library/ms186724.aspx

2. Go the section "Lower-Precision System Date and Time Functions"

3. Notice that the "Return value" column describes CURRENT_TIMESTAMP, GETDATE, and GETUTCDATE as returning datetime2(7), which is not the case. The "Return data type" column properly describes the returned type as datetime.

Actual Results

read the other notes

Expected Results

I expect the contents of the documentation in the "Return value" column to agree with the text in the "Return data type" column of "Lower-Precision System Date and Time Functions".

Platform

 

Virtualization

 
File Attachments
0 attachments
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.

Regards,
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
Sign in to post a workaround.