DBConvert Studio. Synchronize data between the most popular databases.

This video shows a simple step-by-step scenario for data synchronization between different databases.

DBConvert Studio is intended for DBAs who need complex migrations and synchronization between the most popular DBMS.

DBConvert Studio supports the most popular on-premises databases and Database Cloud platforms. It becomes a brilliant all-in-one solution, combining robust database migration engines with a user-friendly interface.

DBConvert Studio supports more than ten of the most popular on-premises databases, including
SQL Server,
MySQL,
PostgreSQL,
Oracle,
Interbase,
IBM DB2,
and more.

For large amounts of storage, it might be wise to consider migrating your databases to one of the following Cloud platforms using DBConvert Studio:
Amazon RDS / Aurora,
Microsoft Azure SQL,
Google Cloud SQL,
and Heroku Postgres.

Read more about DBConvert Studio at https://dbconvert.com/dbconvert-studio

---

Closed Caption:

This video demonstrates simple synchronization between databases where data from the source database enters the target.
Click the "arrow" next to the Connect link to expand the list of databases/ schemas from the dropdown list. Click the "orange db icon" to add this database as a source.
Click the arrow next to another database connection to expand the list of available databases/ schemas. Select different database as the target by clicking the "blue db icon".
Now expand the list of tables in the source database by clicking the arrow button and select only the tables you want to synchronize from the list.
Click "customization" in the lower right corner to configure additional sync options. A pop-up dialog prompts you to name the job to save current settings.
A new tab opens automatically. Various configuration options are offered here.
Check the boxes next to the items to select/ deselect individual tables/ fields to include or exclude from synchronization.
Check all "Insert Sync," "Update Sync," and "Drop Sync" options to get an entirely identical source and target databases.
Click the "commit" button to start the actual conversion process. A pop-up window shows the current progress of operations.
Now let's check the log of the last operation.
As you can see, the program has created several triggers that help to significantly speed up further synchronizations.
Now start synchronization again.
The latest log shows that previously created triggers now track all changes and only update new records in the target database.
If you decide not to use triggers anymore, you can safely remove them from the database. Just uncheck "Trigger-based sync" check box.
Click commit to start syncing again.
Click the "Process History" link to view logs.
Now all triggers are deleted.