Assume that you use SQL Server Managed Backup to back up databases to Microsoft Azure in Microsoft SQL Server 2016 or 2017. After you install the Cumulative Update 2 for SQL Server 2016 SP1 to address the issue that's described in KB 4014002, when you execute the Managed Backup function managed_backup.fn_available_backups, you may receive an error message that resembles the following:

Violation of UNIQUE KEY constraint 'ConstraintName'. Cannot insert duplicate key in object 'TableName'. The duplicate key value is (ID, DateTime, first_lsnValue, DB).

The statement has been terminated.


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

       Cumulative Update 1 for SQL Server 2017

       Cumulative Update 5 for SQL Server 2016 SP1

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 updates for SQL Server 2016


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.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!