merge and identity column screw up

[Darin]

Publisher w/ 2 subscribers running merge replication.

the data was on all three machines and the i changed tables on the
publisher so the identity column was in a different range. i wanted it
to be an increment of 2 and a seed of 100,000, but instead i set an
increment of 100,000 and a seed of 2.

well, now i need to get the identity columns correct, but they have
already done entries that wrote the larger identity columns (so i have
100,002, 200,002, 300,002, etc).

most of the tables that use identity columns those are just there for
primary key reasons, but there are some that the identity column in
table A is stored in table B so table B can join directly with a single
record in table A.

So, i need to change the identity columns and get them setup correctly,
and then adjust any of the linked identity columns, AND i need to get
those changes down to the other two subscribers.

Any ideas? i haven't done much w/ the dbcc checkident to know 100%
exactly what it will do. i am going to run some tests using that with
the RESEED and new_reseed_value options to see what happens.

but any help would be greatly appreciated.

Darin

*** Sent via Developersdex http://www.developersdex.com ***