Results 1 to 2 of 2
  1. #1
    Join Date
    May 2003

    Post Unanswered: Identity paradox

    We have a problem with replicated tables.

    We have on publisher and one subscriber(using Merge-replication). In our database there is one table with an identity column. In our publication we are using identity ranges in order to make sure that no identical records are created on both the server and the clients.

    So far everything works fine. it is possible to create new records on the server and the clients without any conflicts.

    But, when we tries to insert a record that is out of range on either the server or the clients we got an error; "The identity range managed by replication is full and must be updated by a replication agent. The INSERT conflict occurred in database 'Client1', table 'W_Person', column 'ID'. Sp_adjustpublisheridentityrange can be called to get a new identity range."

    When not using replication it is possible to use SET IDENTITY_INSERT <table> ON. Is there any workaround without using the stored procedure Sp_adjustpublisheridentityrange?

    //John & Peter

  2. #2
    Join Date
    May 2002

    RE: Identity Paradox

    There is a check constraint created on the published table which prevents an value that doesn't meet the criteria of the check constraint from being entered into the identity column.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts