Should /include:missing reseed?

LittleColin

I'm trying to only INSERT data that exists in the source table but doesn't exist in the destination so I used the /include:Missing which seems to almost do what I want (via the command line).

It correctly generates INSERT statements and uses identity insert and correctly does not generate update or delete statements.

However it reseeds the identity based on what was in my snapshot of the production database which is out-of-date by the time we actually perform the rollout and is not necessary.

1. Does the command line allow me to disable the Reseeding?
2. Perhaps it's worth preventing a reseed by default when the /include:Missing switch is used?

LittleColin

Ah I think the documentation is incorrect.

http://www.red-gate.com/supportcenter/C ... 700076.htm

This shows that ReseedIdentity is not a default option but it does appear to be. By specifying the options explicitly (and not specifying ReseedIdentity) I get the result I want.

Simon C

This is indeed something we missed in the documentation; ReseedIdentity is a default option. The full list is:

IgnoreSpaces, IncludeTimestamps, IncludeIdentities, DisableKeys, OutputCommentHeader, ReseedIdentity

Thanks for letting us know; we will update the online documentation and the commandline help in the next release

Simon C