Operational Defect Database
BugZero found this defect 763 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Microsoft SQL Server | 14576382
KB5014047 - Improvement: Match the lock escalation policy for the change tracking table to that of the base table - Microsoft Support
Last update date:
7/13/2022
Affected products:
SQL Server 2019 on Windows
SQL Server 2017 on Windows
Affected releases:
build lower than 15.0.4223.1
Fixed releases:
15.0.4223.1
Description:
Improvement
When change tracking is enabled on a table in Microsoft SQL Server 2019 and 2017, a side table is created to record the changes that occur on the base table. The data is also written to the side table when you run the Data Manipulation Language (DML) statements on the base table. In the current implementation, the policy doesn't apply to the change tracking side table when you disable the lock escalation on the base table. This causes blocking on the side table. This improvement makes the lock escalation policy on the base table also apply to the change tracking side table. Note Enabling and disabling the lock escalation on the base tables is mirrored on the change tracking tables.
Resolution
This improvement is included in the following cumulative updates for SQL Server: Cumulative Update 16 for SQL Server 2019 Cumulative Update 30 for SQL Server 2017
References
Learn about the terminology that Microsoft uses to describe software updates.
