BUG: Inconsistent Timestamp Behavior in Stored Procedure

• Microsoft SQL Server version 4.2 for OS/2
• Microsoft SQL Server, versions 4.2, 4.21, and 4.21a

       NT:  881 (4.2)

SYMPTOMS

When you copy a table that has a timestamp column into another table by executing the following queries in a stored procedure, you may get error 273 ("the user cannot insert a non-null value into a timestamp column") the second time you run the procedure.

   SELECT * INTO table1
      FROM table2
      WHERE 1=2
   INSERT INTO table2
      SELECT * FROM table1

Then if you drop table2 again and rerun the stored procedure, it works correctly.

It always works correctly when SQL Server does not copy the timestamp columns from table1 but instead creates new timestamp columns.

WORKAROUND

In the INSERT statement, list all table1's columns except the timestamp column.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 4.2 for OS/2 and Microsoft SQL Server versions 4.2, 4.21, and 4.21a. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.