Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase ««12

subscriber''s records disappear with merge replication Expand / Collapse
Posted Friday, January 27, 2006 5:22 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Sunday, April 26, 2015 7:11 PM
Points: 339, Visits: 391

The snapshot is created based on the publishing database, and you do have the option of not applying this to the subscribing database(s) if you so desire.

As per previous emails, both databases must be exact copies, so depending on the amount of data in the databases, you may want to perform this task before replication is active, otherwise the only other option is to apply the snapshot during replication.

Post #254037
Posted Wednesday, August 22, 2012 7:45 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, February 5, 2016 9:41 AM
Points: 41, Visits: 221
I suggest you to investigate the "@allow_partition_realignment" publication parameter.
Yu can set it via sp_addmergepublication / sp_changemergepublication

It allows/prevent data at the subscriber (which are not part of the correct partition).

True : sends deletes to the Subscriber to reflect the results of a partition change by removing data that is no longer part of the Subscriber's partition. false leaves the data from an old partition on the Subscriber, where changes made to this data on the Publisher will not replicate to this Subscriber, but changes made on the Subscriber will replicate to the Publisher.
Setting allow_partition_realignment to false is used to retain data in a subscription from an old partition when the data needs to be accessible for historical purposes.

Post #1348404
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse