fix merge replication?

I had merge replication setup between 2 servers. I then stopped and
removed replication, made some system changes, then setup replication
again.
But, it turns out all of the data from the publisher hadn't made it to
the subscriber before I removed replication.
Is there a command I can use on the publisher that tells it to look at
all tables and make sure the data between the two machines is
correct/identical. I know I can do a sp_mergedummyupdate, but that
requires I look at all tables and issue the command for each row in
question. I want the system to do it so it can get everything. I don't
want to do the reinitialize because that would take quite a while (the
data is about 1 gig over the internet transfer would be a day or so).
Any other suggestions?
TIA
Darin
*** Sent via Developersdex http://www.codecomments.com ***
Darin,
you could drop the subscription, use redgate's datacompare to synchronize
the data then add the subscriber as a nosync one.
Alternatively you could try sp_addtabletocontents.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I don't know if I did this correctly. I have a table on the distributor
that has 99000 records, on the subscriber there are only 98000. I did:
exec sp_addtabletocontents 'GLDistribution'
It sat for a while and then said it was successfull. But, the Enterprise
manager still says there is no data to merge, and the subscriber still
only has 98000 records.
Darin
*** Sent via Developersdex http://www.codecomments.com ***
|||Darin,
I'd use a linked server to join the 2 tables based on guid. Make it a Left
Outer Join so you can find the publisher records not on the subscriber. As
there are only 1000 of these, you could then do a dummy update on each one
(use a cursor, or have query analyser create 1000 proc calls and run the
resulting script).
This still leaves the worrying issue of how the records got there in the
first place without firing the merge triggers. Check for bulk inserts or fast
loads in DTS which are the normal culprits.
Cheers,
Paul Ibison, SQL Server MVP
"Darin" wrote:

> I don't know if I did this correctly. I have a table on the distributor
> that has 99000 records, on the subscriber there are only 98000. I did:
> exec sp_addtabletocontents 'GLDistribution'
> It sat for a while and then said it was successfull. But, the Enterprise
> manager still says there is no data to merge, and the subscriber still
> only has 98000 records.
> Darin
> *** Sent via Developersdex http://www.codecomments.com ***
>