How to maintain identity column value during SQL bulk copy to another table?

Question

0.00/5 (No votes)

See more:

Hi,

I am doing sqlbulkcopy from one table to another table.
There are so many tables to do that.
I am copying data with for loop for each tables.

But, i am facing with an issue, whenever i copy data from source table to destination table than identity column value is getting changed.

Suppoose there is value like this in identity column of a source table
301
305
605

but when i copy data than it will imported in destination table like that
1
2
3

1) I have tried,
set identity_insert [tablename] ON
//COPY Data from source to destination
set identity_insert [tablename] OFF

2) I have also set SqlBulkCopyOption.KeepIdentity

Any solution will be highly appriciable.

Posted 31-Oct-14 23:08pm

Nirav Prabtani

Updated 1-Nov-14 0:56am

v2

Add a Solution

Comments

OriginalGriff 1-Nov-14 7:21am

Don't "Bump" your question: it's rude and it doesn't help you get an answer. Quite the reverse in fact.
By all means improve your question to help us answer it, but just editing it to move it to the top of the queue is rude.

Mehdi Gholam 1-Nov-14 7:23am

You can't unless you overwrite the destination data.

Maciej Los 1-Nov-14 13:29pm

Does SELECT statement contains ID field?

Thava Rajan 4-Nov-14 2:29am

query please

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Jörgen Andersson · Answer 1 · 2014-11-01T02:27:00

Solution 1

You can bulkinsert using KEEPIDENTITY and then reseed the Identity if necessary.

More info on MSDN.[^]

Posted 1-Nov-14 2:27am

Jörgen Andersson

member86215483 · Answer 2 · 2014-11-03T19:31:00

Solution 2

Hi Nirav
Try not to include the identity column in your source table,
Also when you are inserting into the destination table, do not include the identity column

Posted 3-Nov-14 19:31pm

member86215483

codejet · Answer 3 · 2014-11-04T21:15:00

Can the identity column datatype in the destination table accomodate the identity column data type from the source table. for example if the identity column for the the destination table is tinyint then it will not will be able to accomodate some int values from the source table hence the regeneration.