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

Symptoms
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.
Resolution
This problem was first fixed in the following cumulative update 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:

Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
Learn about the terminology Microsoft uses to describe software updates.
Properties

Article ID: 3161119 - Last Review: 09/22/2016 03:17:00 - Revision: 2.0

Microsoft SQL Server 2014 Developer, Microsoft SQL Server 2014 Enterprise, Microsoft SQL Server 2014 Standard, Microsoft SQL Server 2016 Developer, Microsoft SQL Server 2016 Enterprise, Microsoft SQL Server 2016 Enterprise Core, Microsoft SQL Server 2016 Standard

  • kbqfe kbfix kbexpertiseinter kbsurveynew KB3161119
Feedback