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.
This issue is fixed in the following cumulative updates for SQL Server:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Learn about the terminologythat Microsoft uses to describe software updates.