Merge Replication only 1 way?

[cheyney]

This is my setup:

Publisher/Distributor: sp3-ified SQL Server 2000
Subscriber: sp3-ified MSDE

I have merge replication setup and the subscriber is anonymous. Changes to the database on the publisher side are merged fine into the subscriber database, but changes to the subscriber database are not merged into the publisher database. The agent says "no data needed to be merged."

Whats going on? Aren't changes on both sides supposed to merge into both databases? does it have something to do with being an anonymous subscriber?

Thanks in advance for your help,

Cheyney

 

[JayKusch]

Straight from BOL ...


How to view and resolve merge synchronization conflicts (Enterprise Manager)
To view and further resolve synchronization conflicts

Expand a server group, and then expand a server.


Expand Databases, and then expand the name of the database.


Expand Publications, right-click the publication, and then click View Conflicts.


In the Publications in database list, select the publication to view.


In the Tables with conflicts list, select the table of conflicts to view.


Note Be sure to connect to the correct server to view the conflicts. The location of the conflict table varies depending upon whether replication has been configured for centralized of decentralize logging of conflicts. If centralized, the conflict table is stored at the Publisher and you must connect to the Publisher to view the conflicts. If decentralized, the conflict table is stored at either the Publisher or Subscriber, depending upon which one lost the conflicts.


Thanks

J. Kusch

 

[cheyney]

Thanks, but conflicts weren't my problem..no conflicts were reported, and the data simply wasn't merged. Perhaps my replication triggers were messed up...no matter, I've recreated the publication and subscription and everything is working good now. Weird...

Cheyney