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 |
|
viveksharma
Starting Member
2 Posts |
 Posted - 2004-08-24 : 00:02:03
|
| Hi There,I have been using SQL merge replication for my organisation. The problem is I allocated the range of 10000 for publisher and 100000 for subscribers and threshold is 80%. It is not that we have entered a lot of data but now it says that the identity range is full. It is a surprise how can such a big range be used in a short period of 3 weeks.There are only 5 computers in our office. Also, today one of our manager syncronised his machine with the publisher and it should 1000 updates on publisher from the subscriber. However, the manager reckons that he updated around 5 - 10 records. Please guide.ThanksVivek Sharma |
|
|
Mike2265
Starting Member
6 Posts |
Posted - 2004-08-31 : 06:00:36
|
| That does seem odd.So are you not automatically rolling out new ranges when the threshold is reached? Check what the current identity is with dbcc checkident(<tablename>,'noreseed') and look at the distribution of ids in the ranges to see if you can work out what's happened. Perhaps the identity seed was initially set high - I'm just fishing here.I'm not sure i understand what the second one is. But when you synchronise with the publisher your manager is also going to get all the updates that have been forwarded to the publisher from all other subscribers rather than just his. You also need to consider that any triggers that aren't marked "not for replicaiton" may cause updates on the subscriber which then needs to be resynchronised back to the publisher.cheers,mike |
 |
|
|
|
|
|
merge replication