SQL Flow captures committed changes, produces Fabric Open Mirroring change files, and publishes them through OneLake or a controlled staging path.
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.
The Fabric sink groups source changes into target table specifications and advances its cursor only after its delivery contract succeeds. SQL Flow handles initial snapshot backfill; insert, update, and delete change files; OneLake or local staging workflows; per-destination lag and checkpoint.
Why this path matters
The Fabric sink groups source changes into target table specifications and advances its cursor only after its delivery contract succeeds. SQL Flow handles initial snapshot backfill; insert, update, and delete change files; OneLake or local staging workflows; per-destination lag and checkpoint.
What changes for you
Use the same captured stream for Fabric and other destinations. A Fabric delay accumulates on its own durable cursor. SQL Flow handles independent Fabric backlog and retry; parallel fan-out to other destinations; capture mode chosen by source access; control-plane throughput and health.
The outcome
Tell us the source, table set, Fabric path, and freshness goal. We will map backfill, CDC, and delivery.
The payoff
Oracle, SQL Server, PostgreSQL, MySQL, and Sybase.
Emit Fabric-compatible files with durable progress.
Seed the mirror, catch up, and stay current.
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.
Fabric-native delivery
The Fabric sink groups source changes into target table specifications and advances its cursor only after its delivery contract succeeds.
SQL Flow handles initial snapshot backfill; insert, update, and delete change files; OneLake or local staging workflows; per-destination lag and checkpoint.
One source reader
Use the same captured stream for Fabric and other destinations. A Fabric delay accumulates on its own durable cursor.
SQL Flow handles independent Fabric backlog and retry; parallel fan-out to other destinations; capture mode chosen by source access; control-plane throughput and health.
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.
The Fabric sink groups source changes into target table specifications and advances its cursor only after its delivery contract succeeds. SQL Flow handles initial snapshot backfill; insert, update, and delete change files; OneLake or local staging workflows; per-destination lag and checkpoint.
Use the same captured stream for Fabric and other destinations. A Fabric delay accumulates on its own durable cursor. SQL Flow handles independent Fabric backlog and retry; parallel fan-out to other destinations; capture mode chosen by source access; control-plane throughput and health.
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 the source, table set, Fabric path, and freshness goal. We will map backfill, CDC, and delivery.
Talk through my use case