SQL Virtual Restore is fully flexible and programmable, allowing administrators to perform virtual database restore operations from TSQL, PowerShell, SMO and other interfaces. Additionally, SQL Virtual Restore is fully extensible allowing virtualized restore operations including Full Backups (including multiple file or "striped" backup devices), Differential Backups and Transaction Log Backups.
A straightforward example using the SQL Virtual Restore wizard user interface involving a single full backup file is provided below.

Step 1 - Connect to an instance of SQL Server

Step 2 - Select Backup File(s) to Virtually Restore
Full, differential and/or transaction log backup devices can be provided at this time, for the purposes of this simple example a single full is provided.

Step 3 - Specify Virtual Restore Options
These options include:
- Database Name - The name of the virtualized database to be created
- Virtual Database Files - Locations for the virtual data and log files to be used during the Virtual Restore operation, these are typically only 16MB in size
- Recovery Completion State - The state of the database after recovery, this can be any legal SQL Server database recovery state, including an online state(WITH RECOVERY) or a read only state (WITH STANDBY)

Step 4 - View Summary

View Virtual Restore Operation Progress

Virtual Restore Operation is Complete

Virtualized Database in SQL Management Studio
After the virtual database restore operation is complete you now have a fully functional SQL Server Database running from the backup file or files used in the Virtual Restore operation, without requiring the additional space normally required to perform a restore operation.
Examples of more complex operations will be provided in future articles. For more information or to download a fully functional evaluation copy of HyperBac SQL Virtual Restore 1.0, visit the HyperBac website.






















