SQL Safe Backup: Restore SQL Server Database and Overwrite Existing Database

http://bit.do/dfuhs Secret discount page at HandyBackup.
How to restore SQL Server Database and overwrite existing database in SQL Safe Backup. SQL Safe Backup provides hands-free backup across your SQL Servers. With it, you'll save time and space, reduce failures, and recover quickly. Automate full, differential and transaction log backups and scale to the growth of your business with this best-in-class solution. Learn how to restore a SQL Server database and overwrite an existing database. ——— Transcript: Welcome to Idera Virtual Education. My name is David Terry and today we'll be covering how to recover database over an existing database that's already on the SQL instance. It's one of the common questions that we get in the Idera Support side, why is it that my restores are failing when I'm trying to recover over an R8 system database? It's actually quite simple. There's a basic checkmark that you need to select when you're doing the restore. So, in this case, you can see here the Healthcare database was not restored correctly, error. And you could see down here, it says Use, Replace or With Stopat clause to restore in the restore statement, when overwriting an existing database. Now that can sound complicated but we've tried to make that easy in the restore wizard. So let's try this backup again. When I right click on the database to be restored, select Restore Database and then it's going to ask me the target. In this case, we're going to restore back over the existing database. So I'm going to stick with the same instance in this case, but I can always restore to other instances within SQL Safe. For the purposes of this video, we will restore over to the same instance. Now the next screen is going to ask me where is the backup file that needs to be restored. One of the beautiful things about SQL Safe is that all the backup history is stored in a back end repository database. So if you have the repository database in place, you can always leverage that to identify where the backups are. If for some reason you've lost that backup repository because of the server crash or corruption or whatever it may have been that happened in your environment, you can always browse out to the file system to identify the backup files or to the target server. In our case, we're going to use the repository. The next screen is going to show me a listing of all the different backups that have occurred. In this case, we're going to go with the pink bar here which is my full backup, and then the next screen we're going to talk about Restore As. Because I want to completely recover over the existing Healthcare database, I'm not going to change the name but what I do want to do is select Force Restore or Replace. That's the reason why we got the error in the first restore option. By selecting Force restore, we will overwrite the existing database with the backup file that we've selected. You'll notice you also have some options in here to modify where the data file and the log files are going to reside. Also, what type of recovery do you want this to be in, you know, full accessibility, no accessibility, read only, standby mode. In my case, we're going to do a normal restore so we're going to do a traditional restore over, but in a later video we can also see how we could've done this restore via instant restore, which would give you immediate access to the data even though it may not be completely restored yet. And then finally, notifications if the restore fails, anything, cancels, completes, successful, we can have emails generated over all summary, and then we can hit the Restore button. In this case, you can see that the error is not going to happen, we actually are pretty much finish with the restore already. So, it's a fairly simple method to go ahead and do a replace, just be sure when you're going to the restore wizard, to select the Replace option in the restore wizard. Thank you for your time, enjoy the rest of your day.