"Thirsh" <Thirsh@discussions.microsoft.com> wrote in message
news:84E8CBBA-205C-40D2-9240-4BA9FB4D1404@microsoft.com...
>I replicate data between SQL Server 2000 and SQL CE 2.0 mobile devices. I
> have configured my table in question to have 1,000,000 for the publisher
> range size and 100 for subscribers. I left the default of 80 for the
> percentage where a new range is assigned. The table's primary key field
> is
> set as "Not for Replication".
>
> My problem is that the maximum PK value currently in the table grew to be
> greater than what SQL claims is the next Range Starting Value. When a
> subscriber adds a new record, it is getting assigned a PK value that
> already
> is used at the publisher and as a result, there is a merge conflict and
> the
> record is deleted.
>
> It is my understanding that it is the merge agents responsibility for
> automatically adjusting identity ranges on the publisher. Does anyone
> know
> why a new range is not being assigned when I synchronize (when the agent
> runs)?

"Thirsh" <Thirsh@discussions.microsoft.com> wrote in message
news:0DB624C8-CA74-4507-8094-8BF19BAC02D6@microsoft.com...
> If the "Next range starting value" is reported to be 1001, shouldn't the
> range handed out to the next subscriber be 1001 - 1100?
>
> "Hilary Cotter" wrote:
>
>> it is possible that the range was exceeded too much and it is being
>> incremented but not enough.
>>
>> For example your range is from 1-100. You try 1000 inserts. The first 100
>> make it in, the next 900 are kicked back, but the next identity value
>> (dbcc
>> checkident(tablename)) will be 1001.
>>
>> The next time the merge agent runs, it should increment the range to the
>> next available one which could be 201-300.
>>
>> I can't understand why this is not occuring though.
>>
>> --
>> Hilary Cotter
>> Director of Text Mining and Database Strategy
>> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
>>
>> This posting is my own and doesn't necessarily represent RelevantNoise's
>> positions, strategies or opinions.
>>
>> Looking for a SQL Server replication book?
>> http://www.nwsu.com/0974973602.html
>>
>> Looking for a FAQ on Indexing Services/SQL FTS
>> http://www.indexserverfaq.com
>>
>>
>>
>> "Thirsh" <Thirsh@discussions.microsoft.com> wrote in message
>> news:84E8CBBA-205C-40D2-9240-4BA9FB4D1404@microsoft.com...
>> >I replicate data between SQL Server 2000 and SQL CE 2.0 mobile devices.
>> >I
>> > have configured my table in question to have 1,000,000 for the
>> > publisher
>> > range size and 100 for subscribers. I left the default of 80 for the
>> > percentage where a new range is assigned. The table's primary key
>> > field
>> > is
>> > set as "Not for Replication".
>> >
>> > My problem is that the maximum PK value currently in the table grew to
>> > be
>> > greater than what SQL claims is the next Range Starting Value. When a
>> > subscriber adds a new record, it is getting assigned a PK value that
>> > already
>> > is used at the publisher and as a result, there is a merge conflict and
>> > the
>> > record is deleted.
>> >
>> > It is my understanding that it is the merge agents responsibility for
>> > automatically adjusting identity ranges on the publisher. Does anyone
>> > know
>> > why a new range is not being assigned when I synchronize (when the
>> > agent
>> > runs)?
>>
>>
>>