When you click on database node "Database options" are displayed in the right panel.
For DBConvert Software it looks like:
For DBSync Series:
Overwrite existing database
If a database being copied already exists, this option "Overwrite existing database" specifies whether it will be overwritten (this will cause all data in the target to be overwritten).
Quantization and Bulk insert
If Quantization option is checked out converters and synchronizers are able to handle large-sized databases efficiently.
Programs read a source database, splits the whole record into portions to upload them in course to a destination database.
Trigger and bidirectional sync options.
Trigger based sync algorithm allows replicating data in near real-time by capturing and delivering updates of modified information as the changes occur and providing continuous data synchronization across heterogeneous environments.
Read more information about Triggers.
Bidirectional synchronization is used when it’s necessary to keep all synced databases identical with the up-to-date information collected from all nodes. Data is replicated across all nodes, where all of them actively participate in data exchange.
Look at information about bidirectional synchronization.
NOTE: Trigger option and bidirectional sync option are available for DBSync products only. The following DBSync products support Trigger based Sync option:
- Oracle and MySQL
- Oracle and MS SQL Server
- Oracle and PostgreSQL
- MySQL and MS SQL Server
- MySQL and Firebird
- MySQL and PostgreSQL
- MSSQL and PostgreSQL
- Firebird and PostgreSQL
- MS SQL Server and Firebird
Sync logs.
If "Create Log" option is checked you can track and log everything that happens to the data during the synchronization.
If you check the "Capturing the changes between source & destination"checkbox the log will be represented as Dump file with INSERT statements where all generated queries are stored.
Checking "Store dump for target database back-up" option will create a dump file containing the reverse queries. The data will take the values that were before the conversion took place.
Garbage (special) symbols.
Garbage symbols are special symbols which are required not to be used as they are reserved for MS SQL / MySQL / PostgreSQL / MS Access / Firebird / MS FoxPro / SQLite / DB2 internal purposes. Here you can replace all garbage symbols in the target database. Click at the database name in the left panel. Database Options appear in the right panel where you enter all special symbols, for example "'"\:/*<> -+" in the field "Garbage symbols to replace/remove".
After pressing "Replace all"button you will get a message where you will be offered to choose a correct name. You can confirm the offered name by clicking on "OK" button. If you click "Apply All" all the unwanted symbols will be automatically replaced with the symbol entered in the "Replace with" field. In case you click "Cancel" the name will stay untouched.
Finally, database objects that were previously marked red won't cause any problems.
Global Mapping and Use Case options.
In order to change data types for the whole database globally use the option below.
There are the options to Use lowercase, Use uppercase and Use CamelCase to snake_case shown below.
- If Use lowercase is checked all the names of the database elements will be converted to lower case. For example: "TableName" will be converted into "tablename". And vice versa.
- If Use uppercase is checked all the names of the database elements will be converted to upper case. For example: "tablename" will be converted into "TABLENAME".
- If CamelCase to snake_case is checked all the names of the database elements will be converted to snake_case. For example: "SampleTableName" will be converted into "sample_table_name".
NOTE: These options are available when converting / synchronizing to MS SQL / PostgreSQL / Oracle / Firebird.
Comments
0 comments
Please sign in to leave a comment.