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

Last reviewed: April 30, 1997
Article ID: Q119108

The information in this article applies to:
  • Microsoft SQL Server version 4.2 for OS/2
  • Microsoft SQL Server, version 4.2
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 : kbbug4.20 kbprg SSrvProg SSrvStProc SSrvWinNT
Version : 4.2 | 4.2
Platform : OS/2 WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 30, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.