From RapidSQL
Jump to: navigation, search

Go Up to Available object actions by DBMS

Running a Checkpoint lets you force all dirty pages for the current database to be written to disk. A dirty page is any data or log page which, after being read into the buffer cache, is modified but not yet written to disk. The Checkpoint statement saves time in a subsequent recovery by creating a point at which all modifications to data and log pages are guaranteed to have been written to disk. If the current database is in log-truncate mode, CHECKPOINT also truncates the inactive portion of the log.

Platform Availability

Important Notes

The default permission for executing a checkpoint is the db_owner fixed database role.

To Run a Checkpoint Against One or More Databases

  1. Initiate a Checkpoint action against one or more databases. For more information see Initiating an object operation.
  2. Use the following table as a guide to working through the panels of the Checkpoint dialog
Step Description

Action options

Displays the names of the database(s) you chose.


Displays the DDL generated to execute the Checkpoint operation. For more information, see Preview.

3. Use one of the Schedule or Execute buttons to execute the Checkpoint.