Enabling Transactional Subscriber with Identity Ranges for Updates

Transactional Replication published tables containing Identity Ranges are updated on subscriber via Replication Distribution Agent.  This processes does not increment the subscriber’s table Identity Seed starting value.

If you drop a Subscriber and want to bring it online as an updatable user database, first execute CHECKINDENT reseeding the table to highest value + 1.

DBCC CHECKINDENT({tablename}, RESEED (select MAX (identity column)))