The information in this article applies to:
BUG #: 1319 (Starfighter65) SYMPTOMSWhen inserting into a SQL Server table using the SQL Server Distributed Management Object's (SQL-DMO's) BulkCopy object, automatically incremented values are inserted into the table's identity column based on the identity column's seed. The values in the source file are not inserted into the identity column. This occurs even when BulkCopy's IncludeIdentityValues property is set to True. STATUSMicrosoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. MORE INFORMATION
The BulkCopy object's IncludeIdentityValues property activates
IDENTITY_INSERT so that a source file's values that map to an identity
column in the destination table can be explicitly inserted into the
identity column of a table. Records import properly, but the literal values
in the source file are not inserted into the identity column; rather, new,
incremented values, based on the initial property column's seed, are
inserted.
Setting the IncludeIdentityValues to True should import the following data
into the SQL table like so:
However, it fails to work properly, and actually inserts the data as:
REFERENCES
For more information about the BulkCopy object's IncludeIdentityValues
property, query on "IncludeIdentityValues" in SQL Server Books Online.
Q152801 : INF: Examples of Sp_OA Procedure Use and SQLOLE.Transfer Object Additional query words: error message DMO
Keywords : kbenv kbhw SSrvAdmin SSrvDMO SSrvErr_Log SSrvGen kbbug6.50 |
Last Reviewed: April 9, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |