This paper will shed light on the importance and benefits of database recovery for data administration. The database recovery process restores the database to a previous consistent state. Transaction recovery ensures that transaction logs are written before data is updated. These two aspects will be discussed in detail in the paper.
The Importance of Database Recovery in Administration
Database recovery refers to the process of restoring data to a previous stable state. It is based upon the atomic transaction property. This property states that each transaction is considered a single unit, i.e. each transaction is a single unit of work. All operations must be completed to create consistent databases (On the importance of data backup and recovery, N.D.).
Although it is easy to assume that everything runs smoothly after a new database has been created, once the database is in use, it becomes difficult to manage the database and provide services. These scenarios require that the DBA is fully prepared.
Database managers must understand the importance of data recovery. It doesn’t matter how fast data can be accessed, if data is not recovered then it doesn’t matter how slow or fasts it is.
Today’s data storage is commonplace. Companies store more data than one terabyte or gigabyte on a single server. It is therefore important to have a backup and recovery option as an insurance policy.
The Process for Transaction Recovery
This is the most common method for data recovery in a DBMS. This is also known as a transaction log, journal, or journal. It is made up of logs that keep track of the progress of the transaction from its last consistent state. The database management can see the exact state of the database before and after each transaction. The log truncates when the database returns in a consistent state to erase all omitted transactions. The point when the database returns to a consistent state (check pointing) is called “recovery, N.D.”
This is the process of transaction recovery.
- Transactions that are completed before the checkpoint are not allowed.
- If the transaction is completed after the checkpoint, then the transaction log can be used to redo the transaction.
- ROLLBACK is an option that is not available.