November 26, 2009 at 6:57 am
im using the data import wizard in sql server 2008. I have a copy of a table in a working database on my local server. I want to import all the rows from this table into its counterpart in my dev server. Using the import wizard ive selected the appropriate source and destination tables, selected 'delete rows in destination table' and also 'Enable identity insert'
In sql server 2005 there was a bug that reset the identity columns even though 'enable identity insert' was checked. I dont want to destroy the primary keys in my destination table (they must be the same from the backed up one) so before i start this process, has this bug been fixed in sql server 2008 ? or is there a workaround ?
November 26, 2009 at 8:48 am
I ended up creating another database that was basically a copy of the other (on my local server) and I tried the import process locally. From the results it looks as though the problem is fixed in SQL server 2008, enable identity insert now maintains the values from the identity columns of the imported data
November 29, 2009 at 2:28 pm
You can save the import process into DTSX package and verify the workflow step by step too and detect any problem there.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply