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:

Cumulative Update 7 for SQL Server 2014 Service Pack 1

Cumulative Update 2 for SQL Server 2016 

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 2014

Latest cumulative update for SQL Server 2016 

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.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×