Symptoms
Consider the following scenario:
-
You create a schema and a table in the schema in Microsoft SQL Server.
-
You enable change tracking for that table.
-
You perform manual cleanup by using the sp_flush_CT_internal_table_on_demand command.
In this scenario, the cleanup may fail with an error that states that the table could not be found.
This error occurs because the sp_flush_CT_internal_table_on_demand command does not consider tables with different schemas, such as the tables that are not owned by dbo.
Resolution
This issue is fixed in the following cumulative updates for SQL Server:
Cumulative Update 1 for SQL Server 2017
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
Service pack information for SQL Server 2016
This update is fixed in the following service pack for SQL Server:
Service packs are cumulative. Each new service pack contains all the fixes that are in previous service packs, together with any new fixes. Our recommendation is to apply the latest service pack and the latest cumulative update for that service pack. You do not have to install a previous service pack before you install the latest service pack. Use Table 1 in the following article for finding more information about the latest service pack and latest cumulative update.
How to determine the version, edition and update level of SQL Server and its components
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 terminologythat Microsoft uses to describe software updates.
