FIX: Change tracking cleanup task fails if another database is offline in SQL Server 2014 or 2016

Applies to: SQL Server 2014 DeveloperSQL Server 2014 DeveloperSQL Server 2014 Enterprise More


In SQL Server 2014 or 2016, assume that you have a database that uses change tracking and that auto-cleanup is enabled. If there's a database that's in a non-online state (such as offline or recovery pending), and the value of this database ID is smaller than the ID of the database on which change tracking is enabled, you notice that cleanup of the side table (change_tracking_objectid) does not occur.

Note You experience this issue only when the database ID of the non-online database is smaller than that of the database that has change tracking enabled.


This problem was first fixed in the following cumulative update for SQL Server:


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


Learn about the terminology Microsoft uses to describe software updates.