SET CHECKPOINT
Documentation | Blog | Demos | Support
SET CHECKPOINT
0 out of 5 stars
5 Stars | 0% | |
4 Stars | 0% | |
3 Stars | 0% | |
2 Stars | 0% | |
1 Stars | 0% |
Enables or disables the checkpoint activity over changed buffers.
Syntax
SET CHECKPOINT ON|OFF
Comments
The CHECKPOINT option is set ON by default.
When CHECKPOINT is ON, all data changed in transactions successfully committed by users is sent to a checkpoint file which then is later committed to the database. In this way, the server can guarantee modifications and rollback transactions if some are aborted. It also allows the backup of databases in real time.
When CHECKPOINT is OFF, all data changed in transactions is sent immediately to the database. There is no guarantee of the data being written in case a transaction is aborted. Only one user can perform this kind of operation and the database remains in exclusive access for this user. This options simulates a single-user behaviour and is mainly designed to load big amounts of data as when a fresh database is being created or imported from another version of Zim.
0 out of 5 stars
5 Stars | 0% | |
4 Stars | 0% | |
3 Stars | 0% | |
2 Stars | 0% | |
1 Stars | 0% |