BUG: @@IDENTITY Variable Not Handled Like a Global Variable

Last reviewed: April 15, 1997
Article ID: Q163447

The information in this article applies to:

Microsoft SQL Server, version 6.0

BUG #: 15675 (Windows: 6.0)

SYMPTOMS

The @@IDENTITY value does NOT retain the last inserted value, as documented in the SQL Server Books Online. It is treated more like a function variable, which is inconsistent with the behavior of SQL Server global variables and the online documentation.

To get the last identity value, use the @@IDENTITY global variable. This variable is accurate after an insert into a table with an identity column. However, this value is reset after an insert occurs into a table that does not have an identity column.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 6.0. This problem was corrected in SQL Server version 6.0 Service Pack 3 and later versions.

Additional query words: counter sequence random timestamp generating
Keywords : kbbug6.00 kbfix6.00.sp3 kbusage SSrvGen
Version : 6.0
Platform : 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 15, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.