Just so you understand is it because of a unique constraint (ie: a primary key) that is causing the error. An identity column doesn't care if the value already exists. You can reseed the identity value to a number greater than the max id with:DBCC checkident ('<tableName>', RESEED, <newValue>)Another option is to explicitly add whatever value you want by setting:Set identity_insert <TableName> ONinsert your new valuesSet identity_insert <TableName> OFF
Be One with the OptimizerTG