BUG: Logreader Replicates a Combination of a Delete/InsertLast reviewed: April 15, 1997Article ID: Q155862 |
The information in this article applies to:
SYMPTOMSThe logreader task replicates a delete and a subsequent insert transaction on a particular table as a single update transaction on the subscriber. The necessary conditions are that the delete and insert implicit transactions must be in turn enclosed in an explicit transaction defined using BEGIN TRAN and COMMIT TRAN statements. In addition, the delete transaction must include reference, in the where clause, to the primary key column of the table. If the above conditions are met, the logreader task processes the combination of delete and insert as a singular update that is registered in the MSjob_commands table in the distribution database on the distributor.
WORKAROUNDSeparate the DELETE and INSERT statements into two different transactions by not using the explicit BEGIN and COMMIT TRAN statements.
STATUSMicrosoft has confirmed this to be a problem in Microsoft SQL Server version 6.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
|
Additional query words:logreader replication update insert delete
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |