Transaction log of the CM database rapidly grows until the database stops working

By | October 11, 2020


The transaction log of ConfigMgr database grows to the limit within a short period of time until the database becomes unresponsive. When rebooting the server, the database remains in recovery mode for some time.

You may find entries like the one below in the log of the SQL server:

Change Tracking autocleanup is blocked on site table “Update_ComplianceSummary”. If the failure persists, check if the table “Update_ComplianceSummary” is blocked by any process.


Install the latest cumulative update for SQL. The following CUs are the minimal versions that are supposed to fix issue:

Cumulative Update 7 for SQL Server 2016 SP2
Cumulative Update 4 for SQL Server 2014 SP3


Leave a Reply

Your email address will not be published. Required fields are marked *