OPERATIONAL DEFECT DATABASE
...
...
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: Cumulative Update 16 for SQL Server 2017 Cumulative Update 8 for SQL Server 2016 SP2 Cumulative Update 4 for SQL Server 2014 SP3 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 Latest cumulative update for SQL Server 2014
Learn about the terminology that Microsoft uses to describe software updates.
Click on a version to see all relevant bugs
Microsoft SQL Server Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
