In addition to the basic rules related to databases, tables, and sessions, these rules also affect minimal logging:
You can use minimally logged DMLs only in in-memory or relaxed-durability databases. You cannot use them in databases that have full durability.
The logging mode for a table in a multistatement transaction remains unchanged throughout the entire transaction.
All DML commands are fully logged on tables that participate in declarative or logical referential integrity constraints.
You can export the set dml_login option from a login trigger to a client session. However, unlike most set options, you cannot export set dml_logging from stored procedures or issue execute immediate to their callers, even when you enable set export_options.
All DML commands after a savepoint is set executes with full logging even though the table would have otherwise qualified for minimal logging.
Full logging is performed if any active triggers exist on the table. For DML to run in minimal-logging mode, disable any triggers before executing the DML statement.
An optimizer selecting deferred-mode update processing overrides the minimal DML logging setting, and the DML is executed with full logging.
To support log-based replication, DML on replicated tables always performs full logging.
