Problems with identity range in merge replication.

Hi, I have configured merge replication with pull subscriptions. One of
the articles have an identity column as a primary key. At the begining i
have problems with the use of the identity column so, i defined an
identity range on the article properties. The range i defined was 500000
for each subscribers (there are two). These procedures works fine until
now.
Today, I found that in one of the subscribers i can not insert new rows
with the problems of the violation primary key. If i try to insert the
same row at the publisher it works fine. it means that the identity
range works at the publisher but not at the subscriber.
I found in the books online that i can execute the
sp_adjustpublisheridentityrange system store procedure but i am not
sure about it.
I will appreciate a lot, if someone can help me because now the users
can not use the application.
Thanks a lot for your help.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Use sp_adjustpublisheridentityrange to make adjustment on the publisher.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"mary" <mary@.dbagua.com> wrote in message
news:%23qGYZQX0EHA.1292@.TK2MSFTNGP10.phx.gbl...
> Hi, I have configured merge replication with pull subscriptions. One of
> the articles have an identity column as a primary key. At the begining i
> have problems with the use of the identity column so, i defined an
> identity range on the article properties. The range i defined was 500000
> for each subscribers (there are two). These procedures works fine until
> now.
> Today, I found that in one of the subscribers i can not insert new rows
> with the problems of the violation primary key. If i try to insert the
> same row at the publisher it works fine. it means that the identity
> range works at the publisher but not at the subscriber.
> I found in the books online that i can execute the
> sp_adjustpublisheridentityrange system store procedure but i am not
> sure about it.
> I will appreciate a lot, if someone can help me because now the users
> can not use the application.
> Thanks a lot for your help.
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||Thanks a lot for your help. I execute de sp that you told me but the
problem persist.
Do i have to syncronize the subscriptions or do something else?
Regards,
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Go to your subscriber. Adjust the identity constraint on for the next size.
Something is preventing your subscriber from adjusting the range. You may
have to open a support incident with Microsoft on this one.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"mary" <mary@.dbagua.com> wrote in message
news:ukYybDa0EHA.1256@.TK2MSFTNGP10.phx.gbl...
> Thanks a lot for your help. I execute de sp that you told me but the
> problem persist.
> Do i have to syncronize the subscriptions or do something else?
> Regards,
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||Hi, I apply the second recomendation you give me, it works at subscriber
one but, at subscriber two i get this error:
"The identity range managed by replication is full and must be updated
by a replication agent. The INSERT conflict occurred in database
'Divisas', table 'DivBitacora', column 'Correlativo'.
Sp_adjustpublisheridentityrange can be called to get a new identity
range.
The statement has been terminated."
I did this steps:
1. Execute sp_adjustpublisheridentityrange at the publisher
2. go to subscriber One and in the properties of the design table
options in the check constraints tab get the range that is asigned.
3. Execute the DBCC CHECKIDENT (table, NORESEED)to check the identity
value.
4. Execute the DBCC CHECKIDENT (table, RESEED, rangevalue) to get the
identity value in to the range that is correct.
5. try to insert data and it works fine.
After that, i execute the same steps at subscriber2, but it doesnt
work. I reinicialize the subscription2, but it still doesnt work,
displays the same error.
What could i do to fix the problem at subscriber2?
thanks a lo for your help!!
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!