Microsoft KB Archive/138750

{|
 * width="100%"|

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

 * }

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 : kbprogramming

Issue type : kbbug

Technology : kbSQLServSearch kbAudDeveloper kbSQLServ600