Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


When you run the DBCC CLONEDATABASE command in an instance of Microsoft SQL Server 2014 or 2016, the DBCC CLONEDATABASE command may be unsuccessful. Additionally, you receive the following error message if the database has an object that was originally created in SQL Server 2000:

Database cloning for 'DB_Name' has started with target as 'Clone_DB_Name'.
Msg 2601, Level 14, State 1, LineNumber
Cannot insert duplicate key row in object 'sys.sysschobjs' with unique index 'clst'. The duplicate key value is key_value.


This issue occurs because of a key collision between the default service broker objects in the destination and the user objects in the source.


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

Cumulative Update 3 for SQL Server 2016 SP1

Cumulative Update 5 for SQL Server 2014 Service Pack 2

Note This fix checks the collision and drop service broker objects as needed to prevent this issue.

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 2016

Latest cumulative update for SQL Server 2014


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


Learn about the terminology Microsoft uses to describe software updates.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!