Minimally Logged DMLs

If the values of any of the “ULC Flushes to Xact Log” for “Minimally Logged DMLs” are high, the ULC cannot fully contain the log records for each subcommand that makes up the minimally-logged DML. In this case, Adaptive Server performance does not fully benefit from minimal logging because the log records cannot be discarded. Increase the size of the user log cache size configuration parameter, then re-run sp_sysmon to see if the values for “ULC Flushes to Xact Log” have decreased. A smaller number should indicate that the ULC no longer needs to be flushed to syslogs.


by Full ULC

Indicates that a single subcommand of a minimally-logged DML has logged more log records than can be accommodated within the ULC and must be flushed to syslogs. Minimal logging is only effective if all the log records of a subcommand can be logged within a single ULC. When the subcommand completes and all its log records fit in the ULC, the log records are discarded and are not flushed to syslogs.


by Single Log Record

Single log records cannot live in the ULC, and therefore must cause a ULC flush.


by Start of Sub-Command

Log records from a fully-logged command executed in the same transaction as a minimally-logged DML had to be flushed from the ULC to syslogs before the minimally logged DML was able to start.


by End of Sub-Command

A single sub-command of a minimally logged DML had to be logged because of a previously full ULC, single log record, an so on. The ULC required flushing at the end of the sub-command to preserve all log records of the subcommand.