Microsoft SQL Server databases operate in one of three recovery models: simple, full, or bulk-logged. Most databases use either the simple or full recovery model. It's important to choose the correct recovery model for each of your SQL Server databases.
The most commonly used SQL Server recovery model, the simple model performs no log backups and requires the least amount of administration. Databases operating in the simple recovery model can be recovered up to the point of the most recent full or differential backup. Therefore, data loss exposure increases over time until the next full or differential backup is taken.
For databases using the simple recovery model , increasing the frequency of backups will reduce the potential for data loss.
Databases operating in the simple recovery model automatically manage transaction log data, so you needn't be concerned with excess log file growth.
Databases operating in the full recovery model have the potential to recover to a specific point in time, offering you the potential to design a more flexible disaster recovery plan that includes full and differential backups in combination with transaction log backups.
Log backups need to be performed regularly on databases operating in the full recovery model in order to prevent log files from becoming too large.
The bulk-logged recovery model behaves similarly to the full recovery model, but doesn't permit point-in-time recovery. Bulk operations performed on such databases will use minimal log space and will benefit from improved performance.