Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>GateKiller,</p> <p>In simple terms (and not a copy-paste out of the SQLBOL) so you can understand the concepts:</p> <p><a href="http://www.sqlmvp.org/restore-database-with-norecovery/" rel="nofollow noreferrer">RESTORE WITH RECOVERY</a> uses the backup media file (eg. fulldata.bak) to restore the database to back to the time that backup file was created. In this case, the restore sequence can restore other backups and roll them forward. This is great if you want to go back in time to restore the database to an earlier state - like when developing a system.</p> <p>If you want to restore the database TO THE VERY LATEST DATA, (i.e. like if your doing a system Disaster Recovery and you cannot lose any data) then you want to restore that backup AND THEN all the transaction logs created since that backup. This is when you use RESTORE NORECOVERY. It will allow you to restore the later transaction logs right up to the point of failure (as long as you have them).</p> <p>RECOVERY WITH STANDBY is the ability to restore the database up to a parital date (like NORECOVERY above) but to allow the database still to be used READONLY. New transaction logs can still be applied to the database to keep it up to date (a standby server). Use this when it would take too long to restore a full database in order to Return To Operations the system. (ie. if you have a multi TB database that would take 16 hours to restore, but could receive transaction log updates every 15 minutes).</p> <p>This is a bit like a mirror server - but without having "every single transaction" send to the backup server in real time.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload