|
Home > Archive > microsoft.public.sqlserver.server > October 2002 > Datatype Rowversion
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Datatype Rowversion
|
|
| Sandra Payton 2002-10-05, 9:16 pm |
| The Microsoft SQL server datatype timestamp is not the=20
same as the timestamp datatype defined by SQL-92 standard.
As stated from Microsoft BOL=20
"A future release of Microsoft=AE SQL ServerT may modify the=20
behavior of the Transact-SQL timestamp data type to align=20
it with the behavior defined in the standard. At that=20
time, the current timestamp data type will be replaced=20
with a rowversion data type. Microsoft=AE SQL ServerT 2000=20
introduces a rowversion synonym for the timestamp data=20
type. Use rowversion instead of timestamp wherever=20
possible in DDL statements. rowversion is subject to the=20
behaviors of data type synonyms. For more information, see=20
Data Type Synonyms."
Does anyone know how Yukon will address this matter?
Also, has anyone addressed this in your organization, if=20
so how has it been addressed?
| |
| Tibor Karaszi 2002-10-05, 9:16 pm |
| There is very little public info available on Yukon yet. I very much doubt that you'll find
anything public on this (unless someone is willing to break a heavy NDA, of course).
In general, MS tend to warn at least two versions ahead such a change. My guess is that this
will not change in Yukon (but I don't know, this is only a guess).
The resolution is very simple: use the name "rowversion" instead of "timestamp" for this
datatype.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=...ublic.sqlserver
"Sandra Payton" <sjackson19@yahoo.com> wrote in message
news:acc701c2661e$040eb540$39e
f2ecf@TKMSFTNGXA08...
The Microsoft SQL server datatype timestamp is not the
same as the timestamp datatype defined by SQL-92 standard.
As stated from Microsoft BOL
"A future release of Microsoft® SQL ServerT may modify the
behavior of the Transact-SQL timestamp data type to align
it with the behavior defined in the standard. At that
time, the current timestamp data type will be replaced
with a rowversion data type. Microsoft® SQL ServerT 2000
introduces a rowversion synonym for the timestamp data
type. Use rowversion instead of timestamp wherever
possible in DDL statements. rowversion is subject to the
behaviors of data type synonyms. For more information, see
Data Type Synonyms."
Does anyone know how Yukon will address this matter?
Also, has anyone addressed this in your organization, if
so how has it been addressed?
|
|
|
|
|