Hi, > Is there a way to force a transaction log rotation to make sure that even > changes that do not cause > a new transaction log to be created will get archived at regular intervals?
It can be done but the scenario definitely requires code to do so. The internal function __log_newfile can be used to switch to a new log file. After a checkpoint, the old log file will become unused and eligible for archiving. Cheers, Horst
