How to troubleshoot SQL Server synchronous replication

1. The row was not found at the subscriber when the copied command was applied

workaround: Use system stored procedure sp_browsereplcmds "

Sp_browsereplcmds'xact_seqno_start]     ' xact_seqno_end  ]     ' originator_id]       'publisher_database_id]     '  article_id    ]],    @agent_id agent_id ]    , @compatibility_level Compatibility_level ]

Troubleshooting: At the Distributor-distribution db (distribution)

--The 1th statement will appear in the following two scenarios (A/b)

--a, the row was not found on update

{ call [dbo]. [sp_msupd_dbo table name ]  (.....)}

--b, deleted when the row was not found

{ call [dbo]. [sp_msdel_dbo table name ]  (......}

Understanding Synchronization Stored Procedures:

Workaround (a, update,b, delete ): Add the missing data rows to the Subscriber (add a record based on the error ID above) or import and export the method ( SQL statement synchronization specifies the above ID). (Cause: A missing data row on the subscriber causes the delete or update to not find the data row and error)

--c, error when new

{ call [dbo]. [sp_msins_dbo table ]

Workaround (c, error on new ): Error when new, workaround based on the hint may be the identity value or the primary health ID is not worth the data (delete the Subscriber) or the table structure

How to troubleshoot SQL Server synchronous replication