Operational Defect Database
BugZero found this defect 1317 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Microsoft SQL Server | 12552012
KB4483593 - Snapshot Isolation and Savepoint support added for Availability Group databases on the same instance with DTC enabled in SQL Server - Microsoft Support
Last update date:
6/2/2022
Affected products:
SQL Server 2016 Developer - duplicate (do not use)
SQL Server 2016 Enterprise - duplicate (do not use)
SQL Server 2016 Enterprise Core - duplicate (do not use)
SQL Server 2016 Standard - duplicate (do not use)
Affected releases:
build lower than 14.0.3076.1
Fixed releases:
14.0.3076.1
Description:
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: On-demand hotfix for SQL Server 2017 CU13 On-demand hotfix for SQL Server 2016 SP2 CU4 Cumulative Update Information This improvement is included in the following cumulative updates for SQL Server: Cumulative Update 14 for SQL Server 2017 Cumulative Update 5 for SQL Server 2016 Service Pack 2 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: Latest cumulative update for SQL Server 2017 Latest cumulative update for SQL Server 2016
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.
