Setting Schedule_DisableTXNLogging=1 allows the CLUBUSY.NSF & BUSYTIME.NSF
databases created by server during startup to be created with transaction
Even if the advanced property "Disable Transaction Logging" is
set on templates, and a new database is created from this template, the
property "Disable Transaction Logging" is NOT set on the new
database made from the template; the new db does not inherit this advanced
property. This is by design: The "Disable Transaction Logging"
property is not inherited from templates intentionally. Instead, this must
be set on a per-db instance basis.
This setting is absent by default. The absences has the same effect as
the setting being disabled with a value of "0". The CLUBUSY.NSF
& BUSYTIME.NSF files will have logging enabled by default.
Set the NOTES.INI parameter Schedule_DisableTXNLogging=1 to disable transaction
logging for the Busytime databases clubusy.nsf and busytime.nsf. This parameter
is recommended to avoid performance issues during rebuilds of Calendar
Free Time information.
This setting is available on Domino version 6.0.3 and 6.5.1 and beyond.
Beginning with Domino 8.5, improvements to transactional logging have render
the benefits of this option far less pronounced.
LOG_DISABLETXNLOGGING, MAILBOXDISABLETXNLOGGING, RM_NO_LOG_OBJECTS_IN_MAILBOX
notes 85256E1900527C07, SPR #SLIR5NSRU9 Product - Designer
Task using a lot of CPU
Domino 7 performance in production at IBM on pSeries servers
Domino Configuration Tuner:
This setting is included in the DCT
catalog of best practices.