SEARCH
0-9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Prev | Current Page 114 | Next

James Luetkehoelter

"Pro SQL Server Disaster Recovery"

Telling an
executive or business lead that you need to start the restore process over because the database
did a recovery before you could apply additional backup files will not earn you gold
stars or a prime parking spot. That??™s, of course, if the database is around 10GB or less in size.
If the database is 500GB or more than 1TB, you might be looking for a new job.
nTip In the same way that I would recommend always including a WHERE clause in a DELETE statement to
avoid accidental mass deletion, I also recommend always including the RECOVERY clause, even if it??™s just
restoring a full backup. Even if the default is WITH RECOVERY, I type in this code:
RESTORE DATABASE AdventureWorks
FROM AdWorksDevice
WITH RECOVERY
By explicitly specifying WITH RECOVERY or WITH NORECOVERY every time you execute a
RESTORE statement, hopefully including a RECOVERY clause will become second nature. I
can??™t count how many times early in my career I forgot to specify WITH NORECOVERY. The
process of recovery brings the database back online, so you don??™t need to apply any further
differential or log backups.


Pages:
102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126