This topic describes how to restore a database backup by using dbForge Fusion for SQL Server.
After connecting to a required instance of the Microsoft SQL Server Database Engine, in Database Explorer, click the server name to expand the server tree.
Either select a user database or expand the System Databases folder and select a system database.
Right-click the database, point to Tasks, and then click Restore. The Restore Database dialog box appears.
On the Source and Target page, use the Source for restore section to specify the source and location of the backup sets to restore.
Select one of the following options:
Select the database to restore from the drop-down list.
Select to specify a path to a backup file.
In the Destination to restore section, the Database box is automatically populated with the name of the database to be restored. To change the database name, enter the new name in the Database box.
In the Restore to box, leave the default as To the last backup taken or click Timeline to access the Backup Timeline dialog box to manually select a point in time to stop the recovery action.
In the Backup sets to restore grid, select the backups to restore. This grid displays the backups available for the specified location. By default, a recovery plan is suggested. To override the suggested recovery plan, you can change the selections in the grid. Backups that depend on the restoration of an earlier backup are automatically deselected when the earlier backup is deselected.
Optionally, click the Files page to access the Browse Files dialog box. From here, you can restore the database to a new location by specifying a new restore destination for each file in the Restore the database files as grid.
To view or select the advanced options, on the Options page, in the Restore options panel, you can select any of the following options, if appropriate for your situation:
RESTORE WITH RECOVERY is the default behavior which leaves the database ready for use by rolling back the uncommitted transactions. Additional transaction logs cannot be restored. Select this option if you are restoring all of the necessary backups now.
RESTORE WITH NORECOVERY which leaves the database non-operational, and does not roll back the uncommitted transactions. Additional transaction logs can be restored. The database cannot be used until it is recovered.
RESTORE WITH STANDBY which leaves the database in read-only mode. It undoes uncommitted transactions, but saves the undo actions in a standby file so that recovery effects can be reverted.
Take tail-log backup before restore will be selected if it is necessary for the point in time that you have selected.
If there are active connections to the database, restore operations may fail. Check the Close existing connections to destination database option to ensure that all active connections between dbForge Fusion for SQL Server and the database are closed.