Synchronizing one table at a time is fine for ten tables. For three hundred, it isn't. The new Replicator tab, released on 16 October, copies a whole set of tables in one run.
What it does
- Pairs tables between source and target and runs the ticked ones.
- One run, many tables, with a result per table (rows inserted, updated, failed).
- Order you control: parents before children. In a full load with foreign keys, child tables are cleared
before their parents, and the run refuses to delete anything outside the selected list.
- A command-line job for the whole set, to run on a schedule like any other dbSlice job.
- Record Diff after the run: a key check on every replicated table.
NoSQL as a target
The same release added MongoDB, Cassandra, Elasticsearch, Couchbase and Redis as targets of Synchronize and the Replicator, from SQL Server, PostgreSQL and the other relational sources. Useful to feed a search index, a cache or a document store from the system of record.
Replicator or Synchronize?
| Need | Use |
|---|---|
| Many straightforward table pairs | Replicator |
A filter, a mapping, masking or a SELECT as source | Synchronize |
| Resume one interrupted table | Synchronize |
The full guide, with every option, is in Replicate several tables in one run. The free version is on the Microsoft Store; writing to a target needs a Desktop or Server license.
