Replication · Docs · Migratrix
Sign in
Docs

Replication

  1. Choose a source and a target connection, database and schema. Both must be SQL Server or Oracle. Targets are limited to environments where you may manage replicas.
  2. Pick the tables. Each needs a primary or unique key; keyless tables are refused. The wizard checks the source first and lists what it needs (SQL Server: CDC enabled and the Agent service running; Oracle: ARCHIVELOG and supplemental logging).
  3. Across engines, review the mapping Conversion Studio proposes. Overrides stay with the replica and can be edited later on its Mapping tab.
  4. Decide whether to create the target tables or reuse existing ones (emptied first). Foreign keys and triggers are held back until Promote.
  5. Set batch size, poll interval, a lag threshold, a reject threshold and the alert recipients. Start now or later.

States: Loading, Streaming, Waiting, Retrying, Paused, Failed, Promoted. A paused replica carries a reason; a schema change on the source pauses with the diff and offers Accept change or Resync. Resync can also be run per table while the others keep streaming.

Rejected rows are listed with the target's reason. Retry re-reads the current source row by key and applies it; Dismiss closes it. A consistency check compares rows by key (same engine, up to 20,000 per table) or row counts (cross-engine).

Alerts: lag over the threshold, a state change, repeated retries and rejects over the threshold. They reach the recipients in the product, by email and Slack where the environment has a channel route, and a per-workspace webhook signed with HMAC-SHA256.

Where state lives: the definition is encrypted on the Executor; checkpoint, events and the run lease sit in a _migratrix schema on the target. The control plane receives status and metrics only. Permissions are per environment: Replicas read, operate, manage, admin.

Promote applies the held-back constraints, drops the source capture and stops the replica; the target is then the system of record. DDL is not replicated. Licensed in the Scale plan. A Conversion Studio run with change capture can be stopped and continued as a replica from its checkpoint: Conversion Studio. Product page: Replication.