I have a system that comprises two MS Sql server database servers with merge replication configured.
The publisher publishes a table that has a primary key of type integer that is an identity columne with a seed of 1 and an increment of 1.
All data updates are performed at the subscriber under normal circumstances.
Periodic archiving results in the deletion of records from the publisher and the replication functions as expected, resulting in the same deletions at the subscriber database.
An incident occurred which required taking the publisher off line and continueing with the subscriber database for a short period. primary key did not continue with the expected values that would follow on (autoincremented) from the records in the publisher database. Instead, the values continued from a lower value as if the system was attempting to fill in the numbers that had been previously deleted.
This poses a problem due to the loss of referential integrity.
Goe can i configure the publisher/subscriber so that the auto-incremented columne in the table continues contigiously regardless.
when new records were added to the subscriber tale however, it was observed that the