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.
This issue is fixed in the following cumulative updates for SQL Server:
Service pack information for SQL Server 2016
This update is fixed in the following service pack for SQL Server:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.