03-26-2013 06:25 PM
Hi, I've been doing backups on our database for a while (which has come in handy a few times!), but I am wondering if there is a good way to test backup files to make sure they are working properly and that they are not corrupt. I have had experience with our remote databases only being able to be restored 1 time, and I'm afraid if I restore a backup that I would not be able to do it again later if I needed to.
Also, does it make any difference with how the SQL server functions if I restore a backup once a month to check it? I am assuming if I went in afterwards and deleted the database it would be OK, but I think if we left the restored databases in there it would cause issues with how well our main database runs from day to day. Any suggestions or best practices? Thanks!
03-26-2013 06:28 PM
Do a Restore As. That will force you to use a different name for the database and then you can check the quality of the backup.
03-26-2013 06:36 PM
It leaves the backup file, it simply extracts the database from the backup file.
03-26-2013 07:09 PM