Truncates (deletes) the transaction log when a checkpoint is done, either at shutdown or as a result of a checkpoint scheduled by the server.
Truncation provides a way to automatically limit the growth of the transaction log. Checkpoint frequency is still controlled by the CHECKPOINT_TIME and RECOVERY_TIME options (also definable on the command line).
The -m option is useful where high volume transactions requiring fast response times are being processed, and the contents of the transaction log are not being relied upon for recovery or replication. When this option is selected, there is no protection provided against media failure on the device containing the database files.
To avoid database file fragmentation, Sybase recommends that you place the transaction log on a separate device or partition than 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 command-line variable.