SQL Flow now presents bulk movement and continuous replication as peer capabilities on one engine. Release notes keep connector, behavior, deployment, and compatibility changes in one place.
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.
Each entry identifies the affected capability, connector or deployment surface, and any prerequisite, compatibility, or recovery consideration that operators need to carry into an upgrade.
Why this path matters
Each entry identifies the affected capability, connector or deployment surface, and any prerequisite, compatibility, or recovery consideration that operators need to carry into an upgrade.
What changes for you
Check source and target versions, capture mode, schema behavior, durable state, agent placement, and rollback expectations against the support matrix and the release note for the version you intend to deploy. SQL Flow handles connector and type changes; state and recovery changes; security and deployment changes; known limits and upgrade notes.
The outcome
Tell us the deployed version, engines, capture modes, and topology. We will map the relevant release and compatibility checks.
The payoff
Performance, recovery, mapping, and warehouse-loading changes.
Capture, apply, topology, schema, and correctness changes.
Agents, security, deployment, catalog, and control-plane changes.
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.
Release notes
Each entry identifies the affected capability, connector or deployment surface, and any prerequisite, compatibility, or recovery consideration that operators need to carry into an upgrade.
Upgrade planning
Check source and target versions, capture mode, schema behavior, durable state, agent placement, and rollback expectations against the support matrix and the release note for the version you intend to deploy.
SQL Flow handles connector and type changes; state and recovery changes; security and deployment changes; known limits and upgrade notes.
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.
Each entry identifies the affected capability, connector or deployment surface, and any prerequisite, compatibility, or recovery consideration that operators need to carry into an upgrade.
Check source and target versions, capture mode, schema behavior, durable state, agent placement, and rollback expectations against the support matrix and the release note for the version you intend to deploy. SQL Flow handles connector and type changes; state and recovery changes; security and deployment changes; known limits and upgrade notes.
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 deployed version, engines, capture modes, and topology. We will map the relevant release and compatibility checks.
Talk through my use case