Timestamp As Part Of Composite Primary Key?
Solution 1:
don't use the timestamp data type!!
The timestamp syntax is deprecated. This feature will be removed in a future version of Microsoft SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use this feature.
timestamp (Transact-SQL)http://msdn.microsoft.com/en-us/library/ms182776(SQL.90).aspxrowversion (Transact-SQL)http://msdn.microsoft.com/en-us/library/ms182776.aspx
Also, if it primarily designed to change, to keep track of versions, why make it a part of a primary key? changing a primary key can cause many problems!
If you need a system generated value for a primary key, use an identity or guid.
IDENTITY (Property)http://msdn.microsoft.com/en-us/library/aa933196(SQL.80).aspxGUID uniqueidentifierhttp://msdn.microsoft.com/en-us/library/aa260656(v=SQL.80).aspx
Solution 2:
You can work around it.. set
- Auto Generated Value to True
- Auto-Sync to OnInsert
...unless you already have of course
Post a Comment for "Timestamp As Part Of Composite Primary Key?"