FIX: Updates Are Replicated as Delete/Insert Pair Even When Updates Should Not Be Replicated

Article translations Article translations
Article ID: 285127 - View products that this article applies to.
This article was previously published under Q285127
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all


When choosing not to replicate UPDATES (action type = none), a delete/insert pair may still be replicated when the primary key of the record is updated on the publisher. This symptom applies to Transactional Replication only.


Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.


Article ID: 285127 - Last Review: October 23, 2013 - Revision: 2.1
  • Microsoft SQL Server 7.0 Standard Edition
kbnosurvey kbarchive kbbug kbfix KB285127

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from