You may want to have a look at the restore database script on SQL Server Central, and replace the @cmd with SQL Backup specific commands. Here is the link to the script:
There isn't a way to do this automatically within SQL Backup. It was an idea in the beginning, but there is just so much to go wrong -- to wit:
What if the backup location changes and backups are spread across multiple directories
What if the database configuration changes (for instance recovery model)
How to find the latest set of backups, given a folder with a mix of full, differential, and log backups
What to do if the database's logical file locations change -- we could use the server default but that would cause potential performance problems if the database has filegroups spread across multiple drives
How do you recover the master database, especially if it was backed up and then the server upgraded. This would require a rebuild of the server
In a simple scenario, the script from SQL Server Central would work just fine, though.
mmrajesh
Posts: 2
Comments
You may want to have a look at the restore database script on SQL Server Central, and replace the @cmd with SQL Backup specific commands. Here is the link to the script:
http://www.sqlservercentral.com/scripts ... riptid=962
There isn't a way to do this automatically within SQL Backup. It was an idea in the beginning, but there is just so much to go wrong -- to wit:
In a simple scenario, the script from SQL Server Central would work just fine, though.