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:

       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


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.

Har du brug for mere hjælp?

Udvid dine færdigheder
Gå på opdagelse i kurser
Få nye funktioner først
Deltag i Microsoft insiders

Var disse oplysninger nyttige?

Hvad påvirkede din oplevelse?

Tak for din feedback!