Deprecate TIMESTAMP (the keyword, not ROWVERSION itself)
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:
CREATE TABLE dbo.foo
And then expect to do:
INSERT dbo.foo SELECT 1, GETDATE();
This unfortunately named synonym needs to be phased out, because users are not getting any smarter about it.
Upvotes: 62<=-=Dec 13 2007 4:39PM=-=>
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.
Wow 2007. That’s a lot of looking.<=-=May 19 2016 8:41AM=-=>
This is really confusing when the documentation says timestamp is deprecated, yet when you generate the DDL Script it still uses timestamp<=-=Jun 28 2016 7:57AM=-=>
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.