FIX: Access violation occurs when a clone database verification fails in SQL Server 2016, 2017 and 2019

S’applique à : SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise Core

Symptoms


Assume that you run the following command from Microsoft SQL Server 2016, 2017 or 2019 Management Studio (SSMS) against a database with Change Tracking enabled. You notice that the clone of the database is correctly created, but the clone database verification fails and returns the following message. Additionally, you may receive an access violation dump file.
DBCC CLONEDATABASE (AdventureWorks, AdventureWorks_clone)WITH VERIFY_CLONEDB
NO_STATISTICS and NO_QUERYSTORE options turned ON aspart of VERIFY_CLONE.
Database cloning for 'AdventureWorks' has started with target as'AdventureWorks_clone'.
Database cloning for 'AdventureWorks' has finished. Cloned database is'AdventureWorks_clone'.
Database 'AdventureWorks_clone' is a cloned database.
Clone database verification has failed.
DBCC execution completed. If DBCC printed error messages, contact your systemadministrator.

Status


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

Resolution


This issue is fixed in the following cumulative updates for SQL Server:
About cumulative updates for SQL Server:
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:

References


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