No, it is not possible.
You could consider defining a database event that will truncate the transaction log when it reaches a certain size. The sample below, taken from the documentation, limits the size of the transaction log to 10 MB.
CREATE EVENT LogLimit TYPE GrowLog WHERE event_condition( 'LogSize' ) > 10 HANDLER BEGIN IF EVENT_PARAMETER( 'NumActive' ) = 1 THEN BACKUP DATABASE DIRECTORY 'c:\\logs' TRANSACTION LOG ONLY TRANSACTION LOG RENAME MATCH; END IF; END;
Sometimes recovery takes a back seat to administration and performance issues; e.g., when an embedded database is recreated on demand and used for transient data.
You might consider using a DatabaseStart event to confirm that the database was started with -m, and if not, take some action.
AFAIK there is no easy way to determine whether or not -m is in effect, but this code seems to work in Version 12:
SELECT IF PROPERTY ( 'CommandLine' ) LIKE '%-m%' THEN 'Y' ELSE 'N' END IF AS truncate_log_on_checkpoint; truncate_log_on_checkpoint 'Y'
answered 12 Sep '12, 16:40