If your production table is not an identity column, then there is no need to change it to identity column to insert the data. You can add a column in the Staging table that is an identity column which would populate it. Then insert the results into the production table. What I mean is something like shown below. If this does not work for you, can you post the DDL for your production table?-- Create tables-- Parts table. It has an identity column and GUID column.CREATE TABLE Parts(col1 INT, col2 INT, idCol INT NOT NULL , guidCol uniqueidentifier);-- Staging table. It does not have the identity column and the GUID column. --The structure of this table should match the data file.CREATE TABLE PartsStaging(col1 INT, col2 INT);-- Insert some data into the staging table.INSERT INTO PartsStaging SELECT 1,10 UNION SELECT 2,11 UNION SELECT 3,12;-- add the identity column in the staging table and set the starting id to -- whatever you need it to be, for example, 1477alter table PartsStaging add idCol int not null identity (1477,1);-- Script to insert the data from the staging table into the Parts table.INSERT INTO Parts (col1, col2, idCol, guidCol)SELECT col1, col2, idCol, NEWID()FROM PartsStaging; -- cleanup staging table (or you will need to truncate it it before you do the next import). DROP TABLE PartsStaging;-- see what you have in the Parts table.SELECT * FROM Parts