Symptoms

Assume that you have a database that's configured for Managed Backup in Microsoft SQL Server 2016 and 2017. When the name of the database is changed to the same name with a trailing white space, Managed Backup will no longer operate for that database, and this issue cannot be fixed by reconfiguring Managed Backup.

Additionally, when you use any Managed Backup configuration stored procedures after the renaming operation, you may receive an error message that resembles the following:

SQL Server Managed Backup to Microsoft Azure cannot configure the database, 'DatabaseName', because it either does not exist or is offline.

Resolution

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

       Cumulative Update 6 for SQL Server 2017

       Cumulative update 8 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 update for SQL Server 2016

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 terminologythat 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!

×