FIX: Query plans are different on clone database created by DBCC CLONEDATABASE and its original database in SQL Server 2014, 2016 and 2017

Applies to: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise Core


Assume that you use DBCC CLONEDATABASE command to clone a database in Microsoft SQL Server 2014, 2016 and 2017. You may find that the query plans of a columnstore query on the clone database are different from the query plans in the original database.


This issue is fixed in the following cumulative updates for SQL Server:

Cumulative Update 13 for SQL Server 2017

Cumulative update 4 for SQL Server 2016 SP2

Cumulative Update 3 for SQL Server 2014 SP3


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


Learn about the terminology that Microsoft uses to describe software updates.