Hello,
When SQL Data Compare 5 inserts rows into a target table (as a result of missing rows in the target table), identity insert is turned off then back on.
That is ok (even if I would prefer that the script leaves MSSQL deal with the identity value itself but I understand it would greatly complexify the management of foreign key values that points onto the identity field).
What (in my humble opinion) is not ok is that there is no call to reseed the identity column, thus resulting in a potential error once a new record is inserted with identity_insert off (which is the case all the time).
Is there any reason what this is not done ?
Could we at least have an option that says "Reseed table if identity inserts occurred" ?
Thanks !
When SQL Data Compare 5 inserts rows into a target table (as a result of missing rows in the target table), identity insert is turned off then back on.
That is ok (even if I would prefer that the script leaves MSSQL deal with the identity value itself but I understand it would greatly complexify the management of foreign key values that points onto the identity field).
What (in my humble opinion) is not ok is that there is no call to reseed the identity column, thus resulting in a potential error once a new record is inserted with identity_insert off (which is the case all the time).
Is there any reason what this is not done ?
Could we at least have an option that says "Reseed table if identity inserts occurred" ?
Thanks !