Use the SET TRANSACTION DURABILITY statement to specify whether the server uses strict or relaxed durability for transaction logging. For more information, see Durability and logging.
This statement is a solidDB extension to SQL; it is not part of the ANSI standard.
The SET TRANSACTION DURABILITY statement must be executed at the beginning of the transaction and the setting applies to only the current transaction, until the transaction is committed or rolled back.
Parameters, clauses, keywords, and variables
▪ STRICT: A transaction is written to the transaction log as soon as the transaction is committed.
When the transaction durability setting is changed to STRICT, any previous committed transactions (that are not yet written to the transaction log) wait until the SET TRANSACTION DURABILITY STRICT transaction is committed before they are written to the log.
▪ RELAXED: A transaction can wait until the server is less busy, or until multiple transactions can be written to the transaction log together.
Note There is no DEFAULT option in SET TRANSACTION DURABILITY to set the durability to the value that is specified by the Logging.DurabilityLevel parameter. Instead, after the transaction is committed (or rolled back), the server returns to the durability level that was set before the SET TRANSACTION DURABILITY statement was executed.