CHAPTER 5 n CREATING A BACKUP/RECOVERY PLAN 126
A CASE FOR SIMPLE RECOVERY MODE
I??™ve often heard the edict, ???No production database should be in Simple Recovery mode.??? I??™ve read
this in books, magazines, and on web sites. I??™ve listened to colleagues give presentations extolling the
vices of Simple Recovery mode and the virtues of Full Recovery mode. I??™ve seen consultants chastise
customers for not being able to fully recover a database to the point of failure. I??™ve read ???standards???
documents at organizations that internally forbid the use of Simple Recovery mode. Even the model
database??”the template for every new database created??”is set to Full Recovery. I??™ve even lived by
this credo for a time.
I now disagree with my historical self.
A common question on various SQL Server forums is, ???My transaction log is huge! What do I do????
Managing transaction log growth and effectively sizing your database can be difficult tasks, especially
for a database with unpredictable usage patterns.
Inherent Risks
Focusing on keeping the backup time down almost always results in either longer
restore times or a potential loss of data.
Pages:
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258