Snapshot Isolation and Savepoint support added for Availability Group databases on the same instance with DTC enabled in SQL Server

Applies to: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise Core More

Improvement


Assume that you use the AlwaysOn Availability Groups feature in Microsoft SQL Server 2016 or 2017 with DTC_SUPPORT=PER_DB. After you apply this update, you can use Snapshot Isolation and Savepoints for cross-database transactions against Availability Group databases. This applies if all databases that are involved in the transaction are currently hosted on the same instance.

Resolution


On-demand Hotfix Information

This improvement is included in the following on-demand hotfixes for SQL Server:

Cumulative Update Information
This improvement is included in the following cumulative updates for SQL Server:
About cumulative updates for SQL Server:

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


More information


The following are some common error messages that you may encounter before this improvement is implemented:

Error 3996: Snapshot isolation level is not supported for distributed transaction. Use another isolation level or do not use distributed transaction.
Error 3933: Cannot promote the transaction to a distributed transaction because there is an active save point in this transaction.
Error 627: Cannot use SAVE TRANSACTION within a distributed transaction.

References


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