FIX: Explicit Insert of Identity Value in SP Can Cause AV

Last reviewed: May 2, 1997
Article ID: Q138750

The information in this article applies to:

Microsoft SQL Server, version 6.0

BUG# NT: 10308 (6.00)

SYMPTOMS

If you explicitly insert a value into an IDENTITY column inside a stored procedure, it can cause an thread level access violation.

WORKAROUND

Use a batch file instead of a stored procedure if you need to insert a value explicitly into an IDENTITY column.

MORE INFORMATION

Replication scenario:

   use pubs
   go
   create table t(a int identity,b char(5))
   go
   create proc sp_test_t
   as
   insert t(a,b) values(100,'dskfj')
   go
   set identity_insert t on
   go
   sp_test_t

The following batch works fine:

   set identity_insert t on
   go
   insert t(a,b) values(100,'dskfj')

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0. This problem was corrected in Service Pack 2 for SQL Server version 6.0. For more information, contact your primary support provider.

Additional query words: sql6 windows nt id values
Keywords : kbbug6.00 kbfix6.00.sp2 kbprg SSrvProg
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: May 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.