Register now or log in to join your professional community.
In all my projects / implementations, I have prefered to use the full mode recovery model. Most of my implementations were one way or other linked to sensitive financial transactions . In case of a database crash and as part of the recovery strategy, it was very important to restore data even from the last few minutes. This can only be possible from the transaction logs genereated when the SQL database recovery model has been set to full mode.
I have been in actual situations where this has been a life saver.
Data Recovery Models are to controll the data transaction flow into the databse engine.
there are basically 3 type of Recovery models:
1. Simple: Not possible for Point in time recovry, No need to maintain Trans Log backup
2. Full: Point in time recovery possible, must maintain Trans Log back periodically, otherwise we gonna end-up with discspace due to log file size increase
3. Bulk - Logged: Point in time recovery possible, ideal and afficient for the databses where mostly bulk operations performs
I would suggest for production database server/mission critical database, we can set fully recovery mode. Where as dev database we can have simple recovery model if you set this model point in time recovery is not possible.
Recovery models are designed to control transaction log maintenance. A recovery model is a database property that controls how transactions are logged, whether the transaction log requires (and allows) backing up, and what kinds of restore operations are available. Three recovery models exist: simple, full, and bulk-logged.
I would prefer Bulk Logged because -
An adjunct of the full recovery model that permits high-performance bulk copy operations.Reduces log space usage by using minimal logging for most bulk operations. For information about operations that can be minimally logged.
Depends on the requirement.
If the requirement is point in time recovery with bulk input and output, Bulk model is recommended. If the requirement is point in time recovery with bulk input and output then Full recovery model is the best. If there is no need for point in time recovery, simple model is recommended.
I will prefer full recovery model because it will good incase of any failure is happen and we will ge the data point in time and there is a less chance to data loss
as per my side iam using full recovery why because its recovers each and every thing
In computing data recovery is a process of salvaging inaccessible data from corrupted or damaged secondary storage removable files, when the data they store cannot be accessed in a normal way. The data is most often salvaged from storage media such as internal or external hard disk drives, usb flash drives, cd's,dvd's and other electronic device. .
The most common data recovery scenario involves an operating system failure, malfunction of a storage device, accidental damage or deletion, etc. on a single-drive, single-partition, single-OS system...
Simple Recover Model. It will not take long time, it will be sufficient as we take full DataBase Backup periodically as per planned scheduled.
Is one of the mechanisms which controls and manages the growth of the transaction log file. Recovery Model controls how transactions are logged, whether there is automatic log truncation, whether the transaction log requires and/or allows backing up the transaction log, and what kind of restore operations are available.
A recovery model is a database property that controls how transactions are logged, whether the transaction log requires (and allows) backing up, and what kinds of restore operations are available. Three recovery models exist: simple, full, and bulk-logged.