FIX: Syscommittab cleanup causes a lock escalation that will block the syscommittab flush in SQL Server 2014, 2016 and 2017

Applies to: SQL Server 2014 DeveloperSQL Server 2014 EnterpriseSQL Server 2014 Enterprise Core


Assume that you have a database that has change tracking enabled in Microsoft SQL Server 2014, 2016 or 2017. When there are issues that cause delay in syscommittab cleanup, lots of rows in syscommittab may not be reserved. When the issues are fixed, and you try to clean up these records in your transaction, it may take a long time. In addition, the cleanup frequently causes a lock escalation and the table lock will block the syscommittab flush during the checkpoint.


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.