Scripting options affect the way the synchronization script is generated. They are listed under the second tab of the data compare window.
Transaction size - determines the size of the script that will be executed in a single transaction. Depending on the size of the databases/tables being compared the synchronization script may get to be extremely large. Wrapping such large scripts in a single transaction may not be possible due to Oracle limitations, and may not be acceptable for performance and other reasons. For these reasons, sometimes it is necessary to split the script into smaller "chunks" and execute each of those "chunks" as separate transactions.
If the synchronization process is canceled or if it fails, only the current open transaction is rolled back. Changes committed prior to that transaction are permanent and cannot be reversed. To have an unlimited transaction size specify 0 as the max value.
 |
Finding the right transaction size depends on many factors - please adjust this option carefully to suit your specific environment. We recommand, if possible, one unlimited transaction. This ensures that all data changes are either committed or rolled back. |
Log script execution - writes to a file all the SQL statements executed by the data synchronization script.
Disable DML triggers - whether the triggers on tables or views should be disabled while the synchronization script is executed. Triggers are enabled after the script finishes.
Foreign key actions - whether the foreign keys should be disabled, dropped or not touched as all. After the script finishes, the disabled keys are enabled, the dropped keys are created back.
