FIX: Intermittent "row not found" error at Azure SQL DB Subscriber caused by duplication of BEGIN TRAN statements

Applies to: Microsoft SQL Server 2016 Service Pack 1SQL Server 2016 DeveloperSQL Server 2016 Enterprise


Assume that you use Transactionalreplication in SQL Server 2016 or 2017 with Microsoft Azure SQL Database (DB) Subscriber, and youuse multiple subscription streams. With this configuration, when there's a deadlock between the different subscription streams, the Distribution Agent will try to roll back all open transactions, and there will be a retryin single subscription mode. In this situation, you may see an intermittent "row not found" error at the Subscriber.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. 


Cumulative Update Information:

This fix is included in the followingcumulative updates for SQL Server:

About cumulative updates for SQLServer:

Each new cumulative update forSQL Server contains all the hotfixes and all the security fixes that wereincluded with the previous cumulative update. Check out the latest cumulativeupdates for SQL Server:
On-Demand Hotfix Information:

This issue is fixed in the following on-demand hotfix for SQL Server:


Learn about the terminology that Microsoft uses to describe software updates.