BUG: Create Table w/ Multi. Identity Columns Causes Handled AVLast reviewed: May 2, 1997Article ID: Q142078 |
The information in this article applies to:
SYMPTOMSA handled exception may occur if you attempt to create a table with multiple identity columns using SELECT INTO from a table that does not have an identity column. The calling process is terminated and Error 8109 will be generated:
Msg 8109, Level 16, State 1 Attempting to add multiple identity columns to table 'idsinto15_2new', via select into. language_exec: Process 13 generated access violation; SQL Server is terminating this processDB-Library Process Dead - Connection BrokenWORKAROUND Do not attempt to create multiple identity columns on a table because SQL Server 6.0 allows only one identity column per table.
STATUSMicrosoft has confirmed this to be a problem in Microsoft SQL Server version 6.00. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
MORE INFORMATIONSQL Server does not generate an access violation if the 'from' table contains an identity column, correctly reporting only error 8109. Also, this exception occurs only when a statement is executed immediately following the SELECT INTO statement.
|
Additional query words: sql6 identity SP1 servpack regress
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |