May 14, 2003 at 2:45 pm
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
May 15, 2003 at 10:10 am
I don't know if it's too late in your setup but at a conference a while back someone provided a neat solution.
Instance1 Start at 1000, Increment 2
Instance2 Start at 1001, Increment 2
This way they will interleave with each other. Further thought could be to plan for 10, each instance starts at 1000, 1001, 1002 .... and Increment by 10.
Never tried it, but it's sounded interesting.
KlK, MCSE
KlK
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply