Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
PeraPIsar
Starting Member
3 Posts |
 Posted - 2004-11-26 : 06:11:59
|
| Hello everybody.I'm in trouble.The project I am working on is stuck because Sql Server replication isn't working as it should. At least I think so! :-)I have a publisher and three subscribers in a merge replication. I had some problems inserting rows at subscribers because identity ranges were not set. But I set them (every identity value has its range up to 50000). When I initialize the subscriber and try to insert values in it, the following error occures:The identity range managed by replication is full and must be updated by a replication agent. The INSERT conflict occurred in database 'Proba', table 'Cena', column 'IDCena'. Sp_adjustpublisheridentityrange can be called to get a new identity range. But, this cannot be possible because no data has ever been inserted at the subscriber and identity range has been set to a great value.Please help me understand what's going on and to solve problem. I'm in a trouble... |
|
|
ravilobo
Master Smack Fu Yak Hacker
1184 Posts |
Posted - 2004-11-26 : 10:51:27
|
| The idenitity range for all the subscribers and publisher need to be different.for e.g.subscriber1 1- 10000subscriber2 10001- 20000subscriber2 20001- 30000publisher 30001- 40000also NOT FOR REPLICATION clause is required for identity column.------------------------I think, therefore I am |
 |
|
|
PeraPIsar
Starting Member
3 Posts |
Posted - 2004-11-27 : 14:37:15
|
| Thank you for your response.We set the identity range during process of initializing the publication. So we set there for every subsriber the range of 50000 for almost every table. Where should we set different identity ranges for each subscriber? |
|
|
|
PeraPIsar
Starting Member
3 Posts |
Posted - 2004-12-01 : 06:29:23
|
| I've solved the problem.Some old settings for an early ajusted replication remained, so there were some constraints that didn't pass.I didn't know that settings like identity range remain after the replication is deleted. Or did I do something wrong? |
|
|
|
|
|
|
merge replication identity range drives me crazy