BUG: Create/Insert in Stored Procedure Does Not Init Timestamp

• Microsoft SQL Server version 4.2 for OS/2
• Microsoft SQL Server version 4.2x

BUG# OS/2: 1716 (4.2)
       NT:  310 (4.2) 

SYMPTOMS

If a stored procedure creates a table containing a timestamp column and inserts data into the table, the timestamp column will not be initialized, but will just contain NULL. This happens for both temporary tables and permanent tables.

WORKAROUND

Run create/insert as a regular batch, rather than a stored procedure. You cannot as a reliable workaround create the temp table outside the stored procedure. This is because if a second user connection creates the temp table, then executes the stored procedure that inserts into the temp table, then disconnects, the first connection upon creating the temp table and executing the stored procedure will still get NULL values in the timestamp column of its temp table.

STATUS

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

Additional query words: Windows NT

Keywords          : kbprg SSrvProg SSrvStProc kbbug4.20 SSrvWinNT 
Version           : 4.2 | 4.2
Platform          : OS/2 WINDOWS 
Issue type        : 

Last Reviewed: March 20, 1999