Comments on: SQL Server PowerShell : How to Restore SQL Server Databases Using SMO and PowerShell

By: kofco

kofco — Tue, 29 Nov 2011 22:36:39 +0000

Very helpful!
for the logical name this works:

# Get the file list from backup file
$dbFileList = $smoRestore.ReadFileList($server)
$smoRestoreFile.LogicalFileName = $dbFileList.Select(“Type = ‘D’”)[0].LogicalName

$smoRestoreLog.LogicalFileName = $dbFileList.Select(“Type = ‘L’”)[0].LogicalName

Thanks

By: adrian

adrian — Thu, 01 Sep 2011 19:10:27 +0000

This is pure gold. Excellent. This has automated refresh of PROD to TEST to DEV. Outstanding.

By: Jim Schellenberg

Jim Schellenberg — Sat, 04 Dec 2010 03:29:26 +0000

I’m looking for a script that can be pointed to a directory that contains a full backup, perhaps a differential backup as well and many transaction log backups and do a recovery to a point in time or to the end of the logs. If a differential backup is involved then the use of the logs could be limited to after the differential backup.

Has anyone given this a go?

By: Chris

Chris — Tue, 02 Nov 2010 10:43:09 +0000

To kill connections to the database to get exclusive access before restoring add this line:

$server.KillAllprocesses($dbname)

By: Bart Hayes

Bart Hayes — Tue, 02 Nov 2010 06:44:58 +0000

How do you obtain restore details when the backup files have been copied from another server? I’m getting an error on the line
$smoRestoreDetails = $smoRestore.ReadBackupHeader($server). I think because object ‘$server’ is created from the current server but that won’t know anything about a backup file from another server will it?

By: Blog Post: PowerShell: Restoring a whole heap of SQL Databases | IT.beta

Blog Post: PowerShell: Restoring a whole heap of SQL Databases | IT.beta — Sun, 22 Aug 2010 17:48:54 +0000

[...] about 500 databases from their production environment to a development/staging environment. He found this script that should theoretically get the job done but he was running into a few proble…. The problems he was encountering were mostly related to different drive mappings and [...]

By: Will Seitz

Will Seitz — Mon, 16 Aug 2010 12:57:08 +0000

I had some problems with the way you got the logical name. I used instead:

$smoRestoreDetails = $smoRestore.ReadFileList($targetServer) $sourceDb = $smoRestoreDetails.Rows[0]["LogicalName"]

By: Woody

Woody — Thu, 29 Jul 2010 17:15:58 +0000

Absolutely great script! This has really come in handy for me. Thanks so much for sharing it. Can I make a couple of suggestions for Restore to New Database?
1) When determining the Data and file locations you might want to use $server.DefaultFile and $server.DefaultLog. Using $server.Information.MasterDBPath and $server.Information.MasterDBLogPath points to the location of the files for ‘master’ and not necessarily the location of ‘user’ databases.
2) Consider using $DataFiles = $restore.ReadFileList($server) to get the actual Logical file names. Attempting to restore to a constructed logical name, which may be incorrect, results in a restore error.

All in all, still a very helpful script!