SQL
Behavior
The default `CHECKPOINT` command will fail if there are any running transactions. Including `FORCE` will abort any
transactions and execute the checkpoint operation.  
Also see the related [`PRAGMA` option](#docs:configuration:pragmas::force-checkpoint) for further behavior modification.  
#### Reclaiming Space {#docs:sql:statements:checkpoint::reclaiming-space}  
When performing a checkpoint (automatic or otherwise), the space occupied by deleted rows is partially reclaimed. Note that this does not remove all deleted rows, but rather merges row groups that have a significant amount of deletes together. In the current implementation this requires ~25% of rows to be deleted in adjacent row groups.  
When running in in-memory mode, checkpointing has no effect, hence it does not reclaim space after deletes in in-memory databases.  
> **Warning.  ** The [`VACUUM` statement](#docs:sql:statements:vacuum) does _not_ trigger vacuuming deletes and hence does not reclaim space.