Row Count validation fails

I setup transactional replication with automatic updates.
In doing this I did a manual initialization of the schema
by doing a dump and restore of the publisher. When i
validate my subscription i have many tables that dont
pass the rowcount. I think it may be that between my
restore and initilizing the subscription that data may
have chnaged on the publisher? Is there a way to manually
synch up all my tables?
Tim,
there's no way to do this automatically. Manually, you can do a binary
rowcount to determine the non-matching rows, modify them using linked
servers then do your nosyny initialization. This has to be done out-of-hours
to avoid the problem you have already seen.
Allowing the initialization to be produced via the snapshot doesn't have
this problem, as you have the choice of a shared lock on the publisher's
table or a concurrent snapshot, where the data modifications are themselves
logged and passed on to the subscriber.
HTH,
Paul Ibison
|||Sorry - should have said BINARY_CHECKSUM() not rowcount.
Regards,
Paul Ibison