Next Range Starting Value Too High

Hi, I've got a push merge replication set up between two sql servers on the
same domain. I have a table with about 1200 records in it. For some reason
when I publish the article and set the identity range values it chooses a
Next Range Starting Value of over 7000000 when there are only the 1200
records in the table (identity range of 100).
The table constraints at the publisher show the range of 1200 to 1300 but at
the subscriber it shows like 7000000 to 7000100.
Can I change it so that it forces it use a more reasonable number like 1300
to 1400?
When you setup the publication what did you specify as the values of
@.pub_identity_range and @.identity_range parameter to sp_addmergearticle?What
did you set as the identity range values in the UI? I believe you must have
set a very high value for the pub identity range and that is the reason you
are seeing these huge numbers on the subscriber. You can change the
pub_identity_range parameter by using sp_changemergearticle. However that
will not affect the max number that has already been allocated. Next time
you setup the publication use lower values for the @.pub_identity_range
parameter.
Thanks,
Jayanthi
"MBurns" <MBurns@.discussions.microsoft.com> wrote in message
news:577A372C-C296-4214-80D1-2D2BE5A25F97@.microsoft.com...
> Hi, I've got a push merge replication set up between two sql servers on
the
> same domain. I have a table with about 1200 records in it. For some reason
> when I publish the article and set the identity range values it chooses a
> Next Range Starting Value of over 7000000 when there are only the 1200
> records in the table (identity range of 100).
> The table constraints at the publisher show the range of 1200 to 1300 but
at
> the subscriber it shows like 7000000 to 7000100.
> Can I change it so that it forces it use a more reasonable number like
1300
> to 1400?