Operational Defect Database
BugZero found this defect 1308 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Microsoft SQL Server | 10966001
KB4040531 - FIX: Constraint violation error returned by the managed_backup.fn_available_backups function after you install the Cumulative Update 2 for SQL Server 2016 SP1 - Microsoft Support
Last update date:
7/21/2023
Affected products:
SQL Server 2016 Service Pack 1
SQL Server 2016 Enterprise Core - duplicate (do not use)
SQL Server 2016 Enterprise - duplicate (do not use)
SQL Server 2016 Developer - duplicate (do not use)
SQL Server 2016 Standard - duplicate (do not use)
SQL Server 2017 on Windows (all editions)
Affected releases:
build lower than 14.0.3006.16
Fixed releases:
14.0.3006.16
Description:
Symptoms
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.
Resolution
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
