| title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic | ms.custom |
|---|---|---|---|---|---|---|---|---|
Migrate managed backup settings |
This topic covers migration considerations for SQL Server Managed Backup to Microsoft Azure when upgrading from SQL Server 2014 to SQL Server 2016. |
MashaMSFT |
mathoma |
12/17/2019 |
sql |
backup-restore |
upgrade-and-migration-article |
intro-migration |
[!INCLUDE SQL Server] This topic covers migration considerations for [!INCLUDEss-managed-backup] when upgrading from [!INCLUDEssSQL14] to [!INCLUDEsssql16-md].
The procedures and underlying behavior of [!INCLUDEss-managed-backup] has changed in [!INCLUDEsssql16-md]. The following sections describe the functional changes and their implications.
The following table describes some of the key functional differences for [!INCLUDEss-managed-backup] between [!INCLUDEssSQL14] and [!INCLUDEsssql16-md].
| Area | [!INCLUDEssSQL14] | [!INCLUDEsssql16-md] |
|---|---|---|
| Namespace: | smart_admin | managed_backup |
| System Stored Procedures: | sp_set_db_backup sp_set_instance_backup |
managed_backup.sp_backup_config_basic (Transact-SQL) sp_backup_config_advanced sp_backup_config_schedule |
| Security: | SQL credential using a Microsoft Azure storage account and access key. | SQL credential using a Microsoft Azure Shared Access Signature (SAS) token. |
| Underlying Storage: | Microsoft Azure Storage using page blobs. | Microsoft Azure Storage using block blobs. |
There are several benefits to using the new functionality in [!INCLUDEsssql16-md].
-
Block blobs cost less to store.
-
With striping, you can store much larger backups (12 TB versus 1 TB for page blobs).
-
Striping also improves the restore time for large databases
-
For other improvements to [!INCLUDEss-managed-backup] in [!INCLUDEsssql16-md], see SQL Server Managed Backup to Microsoft Azure.
After you upgrade from [!INCLUDEssSQL14], note the following [!INCLUDEss-managed-backup] considerations:
-
Any databases previously configured for [!INCLUDEss-managed-backup] on [!INCLUDEssSQL14] will continue to use the smart_admin system procedures and underlying behavior on [!INCLUDEsssql16-md].
-
The smart_admin procedures are not supported for any new configurations of [!INCLUDEss-managed-backup] on [!INCLUDEsssql16-md]. You must use the new managed_backup procedures and functionality.