Truncates the transaction log when a checkpoint is done, either at shutdown or as a result of a checkpoint scheduled by the
server. This option provides a way to limit the growth of the transaction log automatically. Checkpoint frequency is still
controlled by the checkpoint_time and recovery_time options (or -gc and -gr database server command line options).
The -m option is useful where high volume transactions requiring fast response times are being processed, and the contents
of the transaction log aren't being relied upon for recovery or replication. When this option is selected, there is no protection
against media failure on the device that contains the database files.
To avoid database file fragmentation, it is recommended that where this option is used, the transaction log be placed on a
separate device or partition from the database itself.
This option is the same as the -m server option, but applies only to the current database or the database identified by the
database-file variable.
Caution
Do not use the -m option with databases that are being replicated or synchronized. Replication and synchronization, used by
SQL Remote and MobiLink, inherently rely on transaction log information.
The -m database option must be specified after the database-file, and applies only to that database.
The following example starts a database server named silver and loads the database salesdata.db. When a checkpoint is done, the transaction log contents are deleted.
Syntax