Thanks for answering my question about SQL replication: see below.
From what I am gathering from you, I need to MANUALLY determine which data
is out of sync and then update those rows on the subscriber (by setting a
value to itself?, eg. Update table set datefield=datefield where datefield
= someday) and that will merge in those values. Is this correct?
I think I can do this. It will just be a pain as the remote subscribers
are over a slow link and the database is a couple gigs in size. So
determining which rows are different/missing is going to be difficult. I
suppose I could add a linked server and do a query where the join fails, or I
found a SQL db compare tool from Red Gate software that does DB compares, but
comparing huge databases across slow lines will take forever. Any thoughts?
Thanks again!
[quoted text, click to view] "Hilary Cotter" wrote:
> run a validation. Determine the data which is out of sync/missing. Then
> update the data setting a column to the same value or insert it on the
> publisher if it is missing. Resolve conflicts.
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
>
http://www.nwsu.com/0974973602.html >
> Looking for a FAQ on Indexing Services/SQL FTS
>
http://www.indexserverfaq.com > "James Jegers" <JamesJegers@discussions.microsoft.com> wrote in message
> news:FC72E75B-D4E9-47D3-89EA-8AF0EC863990@microsoft.com...
> > Hello,
> >
> > I have a Merge Replication setup between a publisher and a subscriber.
> > About a month ago the replication failed. We have recently reconfigured
> the
> > replication(recreated the publications, distributors, and each of the
> > subscribers) and got it all going fine now, no errors.
> >
> > My issue is that during that 1 month period while the replication had
> failed
> > and was disabled/deleted there were changes being made at the subscirber.
> > Everything seems to be replicating EXCEPT those changes that were made at
> the
> > subscriber during the down month. I've tring to reapply the snapshots
> with
> > the "upload data" option and all kinds of other stored procedures with not
> > luck.
> >
> > How can I get that data that was entered when the replication links were
> > deleted to resync?
> >
> > Thanks
>
>
