This article was previously published under Q223403
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 18664 (SQLBUG_65)
When running an INSERT/SELECT query that contains a UNION into a table with a timestamp column that has been declared as nullable, two rows will be inserted for each row that qualifies under the select statement. One row will contain a nulled timestamp, the other will contain an actual timestamp.
To work around this problem, declare the timestamp column as NOT NULL.
Microsoft has confirmed this to be a problem in SQL Server 6.5.