SQL Flow supports initial load plus CDC, one-way and multi-master topologies, automatic failover, schema evolution, distributed agents, and mixed destinations.
The job to be done
A capability matters when it removes an operational decision, not when it adds another checkbox. SQL Flow connects source-aware capture, durable progress, target apply, and validation so the page you are reading leads to a usable operating path.
Yes. Seed + Stream catches up from a pinned position. Multi-master lets you choose the conflict winner per table and prevents loops automatically. HA adds leases, fencing, reassignment, and source-aware resume. SQL Flow handles initial load begins a continuous pipeline; one stream fans out to many sinks; choosing the conflict winner per table; failover keeps one fenced owner.
Why this path matters
Yes. Seed + Stream catches up from a pinned position. Multi-master lets you choose the conflict winner per table and prevents loops automatically. HA adds leases, fencing, reassignment, and source-aware resume. SQL Flow handles initial load begins a continuous pipeline; one stream fans out to many sinks; choosing the conflict winner per table; failover keeps one fenced owner.
What changes for you
Agents resolve secrets and move rows locally. Schema changes travel as ordered events. Durable spools absorb target and network outages. SQL Flow handles row data stays in the data plane; outbound agents fit restrictive networks; unsafe DDL pauses visibly; delivery semantics are declared per path.
The outcome
Tell us engines, network, write topology, tables, and recovery objectives. We will answer precisely.
The payoff
Oracle, SQL Server, PostgreSQL, MySQL, and Sybase.
Eleven database, stream, and Fabric sinks.
On-prem, cloud, hybrid, relay-split, and HA.
Where the work happens
Read each capability as part of the operating path. The important question is not whether a feature exists, but what work it removes and what evidence it leaves behind.
Product and topology
Yes. Seed + Stream catches up from a pinned position. Multi-master lets you choose the conflict winner per table and prevents loops automatically. HA adds leases, fencing, reassignment, and source-aware resume.
SQL Flow handles initial load begins a continuous pipeline; one stream fans out to many sinks; choosing the conflict winner per table; failover keeps one fenced owner.
Operations and trust
Agents resolve secrets and move rows locally. Schema changes travel as ordered events. Durable spools absorb target and network outages.
SQL Flow handles row data stays in the data plane; outbound agents fit restrictive networks; unsafe DDL pauses visibly; delivery semantics are declared per path.
Before you choose
Use the page-specific details below as a short discovery checklist. They are the conditions and work areas that shape the capability, not generic product promises.
The path to confidence
The page keeps the product detail close to the decision it supports. Your team can see what the software handles automatically, what it changes for the target, and what the result leaves ready to operate.
Yes. Seed + Stream catches up from a pinned position. Multi-master lets you choose the conflict winner per table and prevents loops automatically. HA adds leases, fencing, reassignment, and source-aware resume. SQL Flow handles initial load begins a continuous pipeline; one stream fans out to many sinks; choosing the conflict winner per table; failover keeps one fenced owner.
Agents resolve secrets and move rows locally. Schema changes travel as ordered events. Durable spools absorb target and network outages. SQL Flow handles row data stays in the data plane; outbound agents fit restrictive networks; unsafe DDL pauses visibly; delivery semantics are declared per path.
Keep the plan connected
A capability becomes easier to operate when the next decision follows from the constraint you just uncovered. Explore the related work that completes this part of the path.
Your working set
Take the next step
Tell us engines, network, write topology, tables, and recovery objectives. We will answer precisely.
Talk through my use case