When you don't want do recreate the whole target database from scratch, use our data change replication and update tables in-place.
If you already have your target database tables, we can compare source table with the target and do a few precise changes to the target to bring it in sync with the source.
Full Convert can't do that. Please take a look at Omni Loader.
The only thing we need is for source tables to have a primary or unique key defined, so we can tell which records are equivalent. If you don't have them on tables you want to synchronize, we allow you to specify custom key.
We support some 40 databases at this point and are very likely to support yours. Take a look at the whole list on our databases page.
We chose not to pollute your databases with hundreds of triggers and log tables. Our solution is clean and supports all popular database engines. Also, we're the only ones efficiently synchronizing non-relational files (CSV, DBF, Excel etc.) with the relational target tables.
Absolutely! Your source database will be used only for reading and is perfectly safe.
Yes! Use the standard conversion project once to create your target database and populate it with your source data. After that, create a data replication project for ongoing sync of the changes.
Please go to the pricing page.
Yes, there is a free trial with full technical support available.Please go to the trial page.
Of course. Please go to the demo request page .
We have copied SQL Server AdventureWorks database to PostgreSQL. At this point source and target databases are exactly the same; source is SQL Server and target is PostgreSQL.
Full Convert detects the changes. As 16 records are missing in the target compared to the source; it's the same as if 16 new records are added to the source so this is the convention Full Convert uses to report changes. Also, one record is changed.
All differences can be examined in Full Convert before applying the change replication. Added records show there is nothing in the target (bottom part of the row), while changed records split only the values that are actually different. We can see that CountryRegionCode and Name are the same for the BA record, while the Modified date differs.
Running the replication will apply the minimal changes to the target database. The script used is a minimal SQL script needed to bring the target in sync with the source database.
Running the comparison again will show that databases are again exactly the same. Often, customers will use the built-in scheduler to do a periodic replication of data changes from source to the target.