How to: Specify that Deletes Should Not Be Tracked (Replication Transact-SQL Programming)
By default, merge replication synchronizes DELETE commands between the Publisher and Subscriber. Merge replication enables you to retain rows in the subscription database even when they have been deleted from the publication, and vice versa. You can programmatically specify that DELETE commands be ignored when creating a new article or you can enable this functionality at a later time using replication stored procedures.
.gif "ms146947.note(ko-kr,SQL.90).gif") 중요: |
|---|
| Enabling this functionality will result in non-convergence, which means that data present at the Subscriber will not accurately reflect data at the Publisher. You must implement your own mechanism for manually removing deleted rows. |
To specify that deletes be ignored for a new merge article
At the Publisher on the publication database, execute sp_add_targetservergroup(Transact-SQL). Specify a value of false for @delete_tracking. For more information, see How to: Define an Article (Replication Transact-SQL Programming).
[!참고] If the source table for an article is already published in another publication, the value of delete_tracking must be the same for both articles.
To specify that deletes be ignored for an existing merge article
To determine if error compensation is enabled for an article, execute sp_helpmergearticle(Transact-SQL) and note the value of delete_tracking in the result set. If this value is 0, deletes are already being ignored.
If the value from step 1 is 1, execute sp_changemergearticle(Transact-SQL) at the Publisher on the publication database. Specify a value of delete_tracking for @property, and a value of false for @value.
[!참고] If the source table for an article is already published in another publication, the value of delete_tracking must be the same for both articles.