I have a strange problem with SQL Server merge replication (push), the publisher is SQL Server 2008 R2 and the sub scriber is 2000. This has been working without any issues for several days, then rows stopped getting inserted into one of the published tables at the subscriber end.
Checking the primary key column on the published table revealed that its seed value had been adjusted but the repl constraint on had not, a simple call to sp_adjustpublisheridentityrange resolved the issue.
Based on this I have two questions:-
1. sp_adjustpublisheridentityrange should have been called automatically (by the merge agent ?), are there any "Usual suspects" in terms of reasons for why this might not have happened ?.
2. Is there any way via any via a view / table I can check whether the identity value and the constraint are not in 'sync', so to speak ?, other than to parse the INFORMATION_SCHEMA.CHECK_CONSTRAINTS VIEW.