<div>
Try to set &quot;IncludeIdentityValues&quot; to false<br />
and then run &quot;set tablename identity_insert on&quot; query<br />
what's happend<br />

</div>


Try to set "IncludeIdentityValues" to false
and then run "set tablename identity_insert on" query
what's happend


<div>
OK, I tried all 4 permutations of BulkCopy.IncludeIdentityVa<wbr />lues = true/false and Database.Execute(&quot;set identity_insert tablename on/off&quot;).<br />
<br />
The resulting exported data file doesn't have any identity values in it, regardless of what I do with these flags. <br />

</div>


OK, I tried all 4 permutations of BulkCopy.IncludeIdentityValues = true/false and Database.Execute("set identity_insert tablename on/off").

The resulting exported data file doesn't have any identity values in it, regardless of what I do with these flags.


<div>
Use the option <br />
-E with bcp (explicit identity) <br />
when loading data, this will allow you to keep the identity column as it comes with the file.<br />

</div>


Use the option
-E with bcp (explicit identity)
when loading data, this will allow you to keep the identity column as it comes with the file.


<div>
<div class="content wysiwyg-content">
I'm using the SQL-DMO BulkCopy object in VB 5 to transfer data between servers. It is important to maintain the existing identity values since they are referenced by other tables, so I set the BulkCopy.IncludeIdentityVa<wbr />lues property to &quot;true&quot; on both the export and import sides, but the identity values are regenerated by SQL Server nonetheless when the import is done. &nbsp;I also tried running the &quot;set tablename identity_insert on&quot; query before doing the import, which normally would allow explicit insertion of identity values, but it made no difference. &nbsp;Any ideas?
</div>
</div>


I'm using the SQL-DMO BulkCopy object in VB 5 to transfer data between servers. It is important to maintain the existing identity values since they are referenced by other tables, so I set the BulkCopy.IncludeIdentityValues property to "true" on both the export and import sides, but the identity values are regenerated by SQL Server nonetheless when the import is done.  I also tried running the "set tablename identity_insert on" query before doing the import, which normally would allow explicit insertion of identity values, but it made no difference.  Any ideas?

DMO: Identity column trashed by bulk copy

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.