This script will get the database restore history details including the files from which the database is restored.
USE [msdb] GO SELECTrs.[destination_database_name], rs.[restore_date], bs.[backup_start_date], bs.[backup_finish_date], bs.[database_name] AS [source_database_name], bmf.[physical_device_name] AS [backup_file_used_for_restore] FROM[dbo].[restorehistory] rs JOIN[dbo].[backupset] bs ON rs.[backup_set_id] = bs.[backup_set_id] JOIN[dbo].[backupmediafamily] bmf ON bs.[media_set_id] = bmf.[media_set_id] ORDER BY rs.[restore_date] DESC GO
Everybody says that the backup process in Azure SQL is very easy. Is that true? In this new article, we will show how to do it.
2016-08-08
1,614 reads
Managing personally identifiable information when moving databases to unsecure environment can be challenging. With this flexible and extendable solution for scrubbing it, you can save yourself some time and effort.
2017-01-13 (first published: 2015-01-06)
15,603 reads
Many DBAs back up their user databases, but not their system databases. Whatever the reason for the lack of a backup, John Grover explains how to save yourself (mostly) should you ever find yourself with no viable master database and no good backup.
2014-07-24
11,798 reads
Display all errors thrown within a catch block by a restore statement in a stored procedure using extended events
2014-06-10
3,728 reads
Mike Eastland frequently restores production databases to various development servers. The drive layouts between the servers are almost never the same. He is constantly shuffling files on his development servers due to space constraints, which in turn breaks the automated restore scripts because the MOVE clauses are invalidated. Does he have to use the MOVE clause every time he does a restore?
2013-12-05
4,001 reads
