Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Recently upgraded from SQL Server 2000 to 2008. When we recreated the Merge Replication we decided to use Automatic Identity Range Management (since it is now the default in 2008). The problem is that we keep running out of ID ranges on the publisher for our busier tables.

My main question is this: When and how does the publisher get a new range assigned?

Our subscribers are set to synchronize every night. I assumed that during this synchronization the identity ranges would be adjusted on both the publisher and subscribers (as the thresholds are exceeded). This does not seem to be the case.

I understand how the thresholds work and they are set with plenty of room for error so long as the identity ranges are adjusted at least once a day.

share|improve this question

migrated from May 12 '11 at 5:18

This question came from our site for professional and enthusiast programmers.

Our subscribers synchronize via sp_addmergepushsubscription_agent (one agent per subscriber). There is also a snapshot agent that runs every 14 days. Do we need to add a merge agent that specifically runs against the publisher? If so, how? – mwolfe02 May 11 '11 at 16:45

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.