Media type | Dialog box | Description |
---|---|---|
File | Locate Backup File | In this dialog box, you can select a local file from the tree or specify a remote file using its fully qualified universal naming convention (UNC) name. For more information, see Backup Devices (SQL Server). |
Device | Select Backup Device | In this dialog box, you can select from a list of the logical backup devices defined on the server instance. |
Tape | Select Backup Tape | In this dialog box, you can select from a list of the tape drives that are physically connected to the computer running the instance of SQL Server. |
URL | Select a Backup File Location | In this dialog box, you can select an existing SQL Server credential/Azure storage container, add a new Azure storage container with a shared access signature, or generate a shared access signature and SQL Server credential for an existing storage container. See also, Connect to a Microsoft Azure Subscription |
Sales
and overwrites the existing Sales
database.Sales
' database. (Microsoft.SqlServer.SmoExtended)'Sales
and creates a new database called SalesTest
. The original database, Sales
, still exists on the server.Sales
, to change to the restoring state.Sales
' has not been backed up. Use BACKUP LOG WITH NORECOVERY
to backup the log if it contains work you do not want to lose. Use the WITH REPLACE
or WITH STOPAT
clause of the RESTORE
statement to just overwrite the contents of the log. (Microsoft.SqlServer.SmoExtended)'.RESTORE
statement already exists on the current server and the specified database family GUID differs from the database family GUID recorded in the backup set, the database is not restored. This is an important safeguard.1:23:17 PM
on May 30, 2016
and shows a restore operation that involves multiple log backups. The database does not currently exist on the server.Sales
from a backup located in the Microsoft Azure storage service. The storage Account name is mystorageaccount
. The container is called myfirstcontainer
. For brevity, the first six steps are listed here once and all examples will start on Step 7.https://mystorageaccount.blob.core.windows.net/myfirstcontainer
. The steps are mostly the same if a SQL Server credential already exists. The database Sales
currently exists on the server. The backup files are Sales_stripe1of2_20160601.bak
and Sales_stripe2of2_20160601.bak
.https://mystorageaccount.blob.core.windows.net/myfirstcontainer
from the Azure storage container: drop-down list if the SQL Server credential already exists, else manually enter the name of the container, https://mystorageaccount.blob.core.windows.net/myfirstcontainer
.https://mystorageaccount.blob.core.windows.net/myfirstcontainer
.Sales_stripe1of2_20160601.bak
and Sales_stripe2of2_20160601.bak
.Sales
database does not currently exist on the server.https://mystorageaccount.blob.core.windows.net/myfirstcontainer
.Sales
database will be restored to the Microsoft Azure storage container https://mystorageaccount.blob.core.windows.net/myfirstcontainer
from a backup located at E:MSSQLBAK
. The SQL Server credential for the Azure container has already been created. A SQL Server credential for the destination container must already exist as it cannot be created through the Restore task. The Sales
database does not currently exist on the server.E:MSSQLBAK
, select the backup file and then click OK.https://mystorageaccount.blob.core.windows.net/myfirstcontainer
, in the text boxes for Data file folder: and Log file folder:.