Merge replication and synchronization

Hi!
i have big problem, i had to remove my merge replication (between Sql2000
MSDE, one way replication only from Publisher to Subsciber). After
recreating this replication, merge agent do not wan't to merge any data, i'm
obtaining NO DATA NEED TO BE MERGED.
i can update all values (by SQL Updatte) in replication tables and merge
will see this data, but what about deletes?
my question is, is it possible to make FULL synchronization between
subscriber and publicator?
thanks
Kuba
It sure is. Let me see if I understand you. You had a working publication
subscriber. You removed the publication. You recreated it, and now the data
does not flow from the publisher to the subscriber, or only updates flow?
How did you recreate the subscriber? At this point it is probably best if
you drop the publication and recreate it, and redeploy the snapshot. Do not
use the no sync option.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Kuba" <k.gluszkiewicz@.citysoftware.com.pl> wrote in message
news:u%23YxQFymEHA.1904@.TK2MSFTNGP09.phx.gbl...
> Hi!
> i have big problem, i had to remove my merge replication (between Sql2000
> MSDE, one way replication only from Publisher to Subsciber). After
> recreating this replication, merge agent do not wan't to merge any data,
i'm
> obtaining NO DATA NEED TO BE MERGED.
> i can update all values (by SQL Updatte) in replication tables and merge
> will see this data, but what about deletes?
> my question is, is it possible to make FULL synchronization between
> subscriber and publicator?
> thanks
> Kuba
>
|||Hi Hilary!
i had a merge replication which works fine
someday i had to remove this replication, i removed subscibers (after that i
used on subscribers sp_mergesubscription_cleanup stored procdure) and next
i removed publication.
after that user whose working on publication machine made a lot of data
changes
after few days i created replication process again (publisher and
subscibers),
now merge agent do not see which records was deleted in publisher database
when my replication was removed, my subscribers inlcudes too many records,
which should be deleted
sorry Hilary for my english, i tried to explain it clearly, i hope you will
understand me
tanks in advance
Kuba
Uytkownik "Hilary Cotter" <hilary.cotter@.gmail.com> napisa w wiadomoci
news:%23nMEWt%23mEHA.3820@.TK2MSFTNGP09.phx.gbl...
> It sure is. Let me see if I understand you. You had a working publication
> subscriber. You removed the publication. You recreated it, and now the
data
> does not flow from the publisher to the subscriber, or only updates flow?
> How did you recreate the subscriber? At this point it is probably best if
> you drop the publication and recreate it, and redeploy the snapshot. Do
not[vbcol=seagreen]
> use the no sync option.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Kuba" <k.gluszkiewicz@.citysoftware.com.pl> wrote in message
> news:u%23YxQFymEHA.1904@.TK2MSFTNGP09.phx.gbl...
Sql2000
> i'm
>
|||Sounds like you didn't re-apply the snapshot at the subscriber...
"Kuba" wrote:

> Hi Hilary!
> i had a merge replication which works fine
> someday i had to remove this replication, i removed subscibers (after that i
> used on subscribers sp_mergesubscription_cleanup stored procdure) and next
> i removed publication.
> after that user whose working on publication machine made a lot of data
> changes
> after few days i created replication process again (publisher and
> subscibers),
> now merge agent do not see which records was deleted in publisher database
> when my replication was removed, my subscribers inlcudes too many records,
> which should be deleted
> sorry Hilary for my english, i tried to explain it clearly, i hope you will
> understand me
> tanks in advance
> Kuba
> U?ytkownik "Hilary Cotter" <hilary.cotter@.gmail.com> napisa3 w wiadomo?ci
> news:%23nMEWt%23mEHA.3820@.TK2MSFTNGP09.phx.gbl...
> data
> not
> Sql2000
>
>
|||dzien dobry.
Your English is better than my Polish
Right click on your merge publication and select view conflicts. This may
explain why some of your data is inconsistent.
I'm still unsure if you did a no sync subscription (the subscriber already
has the schema and data) or not. If you did a no sync, the best way to get
everything in a consistent state is to redeploy your subscription again. If
you did not do a no sync, right click on your publication and reinitialize.
Then start up your snapshot agent, and when it shuts itself down, start up
your merge agent.
if you did a no sync, you should drop your subscription and then either
1) backup your publication database and restore it on your subsciber and
then do another no sync subscription or
2) do a sync subscription (the subscriber does not have the schema and
data).
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Kuba" <k.gluszkiewicz@.citysoftware.com.pl> wrote in message
news:O9P1Uc$mEHA.3896@.TK2MSFTNGP15.phx.gbl...
> Hi Hilary!
> i had a merge replication which works fine
> someday i had to remove this replication, i removed subscibers (after that
i
> used on subscribers sp_mergesubscription_cleanup stored procdure) and
next
> i removed publication.
> after that user whose working on publication machine made a lot of data
> changes
> after few days i created replication process again (publisher and
> subscibers),
> now merge agent do not see which records was deleted in publisher database
> when my replication was removed, my subscribers inlcudes too many records,
> which should be deleted
> sorry Hilary for my english, i tried to explain it clearly, i hope you
will[vbcol=seagreen]
> understand me
> tanks in advance
> Kuba
> Uytkownik "Hilary Cotter" <hilary.cotter@.gmail.com> napisa w wiadomoci
> news:%23nMEWt%23mEHA.3820@.TK2MSFTNGP09.phx.gbl...
publication[vbcol=seagreen]
> data
flow?[vbcol=seagreen]
if[vbcol=seagreen]
> not
> Sql2000
data,[vbcol=seagreen]
merge
>