Managing Identity Ranges

  • Hello everyone. I'm using Transactional replication with queued updating. I had to shut down replication and restart things. Once I restarted replication, I got got errors inserting rows in the subscriber due the violation of the primary key constraint on my identity column. Before starting replication, I dropped the identity range constraings and the msrepl_tran_version thinking that the new itentity ranges would just be created when I started again. It didn't work. The not for replication option is on my identity column. Could this be causing the problem? How can I turn this option off? In addition to dropping the subscription and publication, how can I ststart fresh so that I can get these identity ranges working properly again?

  • The NOT FOR REPLICATION Option needs to be there!

    Can you give us some more info about the Identity Ranges on your Subscribers and your Replication Architecture?


    Kindest Regards,

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply