SQL Server Management Studio can restore a native database backup to a SQL Server instance. This is useful for recovery or creating a separate test copy; it is different from attaching database files or importing a SQL script.
Prepare the restore
Confirm the backup’s origin, SQL Server version and intended recovery point. A backup from a newer SQL Server version cannot be restored to an older version. Encrypted backups or databases require the appropriate recovery certificate or key.
Place the backup where the destination SQL Server service can read it. The file browser concerns the server’s filesystem, which may differ from the computer running Management Studio.
Preserve the current database before any replacement. A live recovery may require a tail-log backup and a sequence of full, differential and log restores; agree that sequence with the database administrator.
Restore a full backup
- Connect to the destination Database Engine in Management Studio.
- Right-click Databases and choose Restore Database.
- Under Source, select Device and open the browse button.
- Choose File, select Add and locate the server-accessible backup. Confirm the device selection.
- Select the intended backup set and review the destination database name.
- On Files, check suitable data and log paths that do not collide with another database.
- Review Options, including the recovery state. Do not enable overwrite unless replacing that database is explicitly intended and backed up.
- Select OK in the main restore dialog to execute the restore, then read the result.
Verify recovery
Confirm the database is in its intended state and check its data. For a completed standalone restore, test application connectivity and mapped logins before redirecting the application. A successful restore message does not prove the application or all required recovery steps are complete.