The checkpoint specifies a time when the DBMS was in a consistent state and all transactions had been committed. These checkpoints are tracked during transaction execution. Transaction log files will be created after the execution. The log file is destroyed when it reaches the savepoint/checkpoint by RECORDING its update to the database. Then a NEW log is produced with the transaction's upcoming execution actions, which is updated until the next checkpoint, and the process continues.

When transaction logs are created in a real-time SETTING, they consume a significant amount of storage space. Keeping track of each update and maintaining it may also take up more physical space on the system. As the transaction log file grows in size, it may eventually become unmanageable. Checkpoints can be used to address this. A Checkpoint is a way for deleting all prior transaction logs and saving them in a permanent storage location.

The following are the advantages of checkpoints:

• It makes the data recovery procedure GO faster.
• The majority of DBMS packages perform self-checkpoints.
• To avoid unnecessary redo operations, checkpoint records in the log file are employed.
• It has very low OVERHEAD and can be done frequently because dirty pages are flushed away continuously in the background.