Deprecate TIMESTAMP (the keyword, not ROWVERSION itself) - by AaronBertrand

Status : 


Sign in
to vote
ID 274333 Comments
Status Active Workarounds
Type Suggestion Repros 5
Opened 4/27/2007 1:56:42 PM
Access Restriction Public


If we can't deprecate this synonym for ROWVERSION, then we need to get better at telling the story that this data type does not store any date or time information.  I am constantly coming across users who do this:

  bar INT,
  [timestamp] TIMESTAMP

And then expect to do:


This unfortunately named synonym needs to be phased out, because users are not getting any smarter about it.
Sign in to post a comment.
Posted by SQLWork on 6/28/2016 at 7:57 AM
The 2016 documentation still says that timestamp will be removed in a later version of SQL Server. So, instead of "timestamp" being the preferred name at least change "rowversion" to be the preferred name. Thus the SQL Server would always report this datatype as "rowversion" instead of continuing to use the misleading and unloved "timestamp". Benefit: Everybody would start seeing "timestamp" and this would encourage converting.
Posted by DevilsChest on 5/19/2016 at 8:41 AM
This is really confusing when the documentation says timestamp is deprecated, yet when you generate the DDL Script it still uses timestamp
Posted by swasheck on 8/14/2014 at 3:56 PM
Wow 2007. That's a lot of looking.
Posted by Microsoft on 12/13/2007 at 4:39 PM
Dear Aaron

Thanks for your feedback. We agree that the original naming of this type was unfortunate (and we can blame our predecessors ;-)). Especially since the name is used in the SQL standard for date/time datatypes.

We are going to look into how we can address this issue in a backwards-compatible way in the upcoming releases.

Please keep the votes coming.