The command SET TRANSACTION DURABILITY {RELAXED | STRICT} controls whether the server uses strict or relaxed durability for transaction logging. This command is a solidDB® extension to SQL; it is not part of the ANSI standard.
The SET TRANSACTION DURABILITY command must be given in the beginning of the transaction. The durability setting applies only to the current transaction, until the transaction is committed or aborted.
If the new transaction durability setting is STRICT, any previous committed transactions that have not yet been written to disk will be written at the time that the SET TRANSACTION DURABILITY STRICT transaction is committed. This means that the pending transaction are not written to disk as soon as the transaction durability level is changed to STRICT; the writes wait until the current transaction that was started with SET TRANSACTION DURABILITY STRICT is committed.
Note There is no DEFAULT option in SET TRANSACTION DURABILITY to set the value to the whatever value the Logging.DurabilityLevel parameter has specified. Instead, after the transaction has been committed (or aborted), the server returns to the durability level that was set before the SET TRANSACTION DURABILITY statement was executed.