solidDB Help : solidDB reference : SQL: Statements : SET TRANSACTION : SET TRANSACTION SAFENESS
  
SET TRANSACTION SAFENESS
SET TRANSACTION SAFENESS {1SAFE | 2SAFE | DEFAULT}
Access requirements
Database user
Usage
Use the SET TRANSACTION SAFENESS statement to specify whether the replication protocol for the transaction is synchronous (2-safe) or asynchronous (1-safe).
1SAFE: The transaction is first committed on the primary server and then transmitted to the secondary server.
2SAFE: The transaction is not committed before it has been acknowledged by the secondary server.
DEFAULT: The transaction uses the protocol that was set with a previous SET SAFENESS statement (see SET SAFENESS), or if no previous statement, then the value set by HotStandby.SafenessLevel (see HotStandby section).
Example
SET TRANSACTION SAFENESS 1SAFE
Go up to
SET TRANSACTION