FIX: AG is suspended when cross-database transaction is applied on AG databases in SQL Server 2016 and 2017

Applies to: SQL Server 2016 Service Pack 2SQL Server 2016 DeveloperSQL Server 2016 Enterprise


Assume that you use Always On Availability Group (AG) in Microsoft SQL Server 2016 or 2017. When you apply cross-database transactions in AG database, an Access violation occurs and then AG is suspended. Additionally, a stack dump and error log may be generated.


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


This issue is fixed in the following cumulative updates for SQL Server:

About cumulative updates for SQL Server:

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:


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