Siebel Remote and Replication Manager Administration Guide > Extracting and Initializing a Remote Database > Options for Extracting the Server Database >

Using a Transaction Log to Optimize Performance

When operating without a transaction log, SAP SQL Anywhere must use a checkpoint at the end of every transaction. Writing these modifications consumes considerable resources, and it can degrade performance.

NOTE:  For Siebel Innovation Pack 2015, the local database for Siebel Mobile Web Client uses SAP SQL Anywhere. SAP SQL Anywhere is not available for new deployments after September 2015. For more detailed information on how this change affects Siebel Tools and Siebel Remote, see Siebel Release Notes on My Oracle Support for Innovation Pack 2015 (Doc ID 1996273.1).

To enable SAP SQL Anywhere to write notes that detail modifications as they occur, you can use a transaction log. SAP SQL Anywhere can write the new database pages all at one time and at a time that is more efficient. Checkpoints make sure information enters the server database file and that this information is consistent and up to date.

To use a transaction log to optimize performance

1. Open the Server Manager command line.

   For more information, see Opening the Command Line Interface for Server Manager.

2. Enter the following command:

   srvrmgr> change param ClientDbTxnLog=True for comp dbxtract

   This command sets the ClientDbTxnLog parameter to True for the Database Extract server component. Subsequent database extracts include a transaction log.