Enabling Transactional Subscriber with Identity Ranges for Updates

Share this Post

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)))

Share this Post

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.