Symptoms

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.

Resolution

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

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

Latest cumulative update for SQL Server 2016

Latest cumulative update for SQL Server 2014

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 that 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?

Any additional feedback? (Optional)

Thank you for your feedback!

×