The recovery model for a database determines how much data the SQL Server engine needs to write to the transaction log, and whether or not a point-in-time restore can be performed. In the event that a transaction needs to be backed out, or the database crashes for some reason, the transaction log is used to restore the database to a consistent state. The SQL Server engine uses this log to maintain the integrity of the database.
The transaction log is a detailed log file that is used to record how the database is updated for each transaction. The recovery model setting determines what backup and restore options are available for a database, as well as how the database engine handles storing transaction log records in the transaction log. SQL Server has three different recovery models: Simple, Full, and Bulk-Logged. Understanding the SQL Server Recovery ModelsĮach database within SQL Server has a recovery model setting. The recovery model of a database determines the types of database backups that can be taken, which in turn determines the different points in time in which a database can be restored. Part of a good database recovery plan is to first understand what recovery models are available. If a DBA can’t recover a database when a disaster strikes, then they better dust off their resume and start looking for a new line of work. The recovery model of a database determines the options a DBA has when recovering a database. The #1 task that every DBA needs to be able to perform perfectly is to recover a database should it become corrupted for some reason. Understanding SQL Server Recovery Models - Simple Talk
0 kommentar(er)
