Are you working with a Sybase/Microsoft timestamp, meaning a binary widget that changes automagically whenever something in the database changes, or a SQL-92 timestamp which is a conventional datetime value that is automagically deposited once when the row is created? The difference is crucial to the answer to your question.
don't apologize, this is, after all, the Microsoft SQL Server forum
what pat was thinking about was this --
Originally Posted by BOL
The Transact-SQL timestamp data type is not the same as the timestamp data type defined in the SQL-92 standard. The SQL-92 timestamp data type is equivalent to the Transact-SQL datetime data type.
A future release of Microsoft® SQL Server™ 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 Server™ 2000 introduces a rowversion synonym for the timestamp data type. Use rowversion instead of timestamp wherever possible in DDL statements.
Insert into Test values ('blah','blah',DEFAULT,'blah') and that seems to have created a unique value.
Do you think that is fine?
yes, but i think it's better to list the specific columns you're providing values for, and therefore you would omit the timestamp column --
Insert into Test (col1,col2, col4) values ('blah','blah', 'blah')