Burst Load source and target roles, CDC modes, hosting, log access, recovery, replica identity, supplemental logging, keys, and apply profiles can all change behavior.
trialstarter{...}activescaleUNCHANGED_TOASTThe 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.
Choose an engine and SQL Flow uses one shared catalog to understand its role in the movement. The catalog identifies Burst Load sources and targets, CDC readers, relational destinations, supported types, and the capabilities that belong to each path. That same information follows the project from setup through execution, so SQL Flow can select the right behavior without making you reconcile connector details across separate tools.
Why this path matters
Choose an engine and SQL Flow uses one shared catalog to understand its role in the movement. The catalog identifies Burst Load sources and targets, CDC readers, relational destinations, supported types, and the capabilities that belong to each path. That same information follows the project from setup through execution, so SQL Flow can select the right behavior without making you reconcile connector details across separate tools.
What changes for you
Connect the source and target. SQL Flow selects the reader that fits the engine and access model, then carries the source contract through the entire pipeline. Behind the scenes, SQL Flow handles before-images, schema changes, truncates, LOBs, logging, and recovery behavior according to what the source supports. It uses that information to resume cleanly and keep the target current, including when the source runs as a managed service.
The outcome
SQL Flow uses the source, target, versions, types, keys, hosting model, and movement pattern to select the right path and surface compatibility risks before production work begins.
The payoff
Confirm Burst Load and CDC capabilities from one source.
Validate the exact capture or loading interface.
Preserve values or surface a visible incompatibility.
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.
Shared catalog
Choose an engine and SQL Flow uses one shared catalog to understand its role in the movement. The catalog identifies Burst Load sources and targets, CDC readers, relational destinations, supported types, and the capabilities that belong to each path.
That same information follows the project from setup through execution, so SQL Flow can select the right behavior without making you reconcile connector details across separate tools.
CDC source contract
Connect the source and target. SQL Flow selects the reader that fits the engine and access model, then carries the source contract through the entire pipeline.
Behind the scenes, SQL Flow handles before-images, schema changes, truncates, LOBs, logging, and recovery behavior according to what the source supports. It uses that information to resume cleanly and keep the target current, including when the source runs as a managed service.
Target contract
SQL Flow maps scalar, temporal, binary, JSON, and engine-specific values into the target dialect. It sizes types around the keys and values that actually need to survive the move, normalizes identifiers where the target requires it, and makes unresolved mappings visible before they become bad data.
The result is a target contract SQL Flow can apply, validate, and recover against. You get a destination that behaves as designed instead of discovering incompatibilities after the load has started.
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.
Choose an engine and SQL Flow uses one shared catalog to understand its role in the movement. The catalog identifies Burst Load sources and targets, CDC readers, relational destinations, supported types, and the capabilities that belong to each path. That same information follows the project from setup through execution, so SQL Flow can select the right behavior without making you reconcile connector details across separate tools.
Connect the source and target. SQL Flow selects the reader that fits the engine and access model, then carries the source contract through the entire pipeline. Behind the scenes, SQL Flow handles before-images, schema changes, truncates, LOBs, logging, and recovery behavior according to what the source supports. It uses that information to resume cleanly and keep the target current, including when the source runs as a managed service.
SQL Flow maps scalar, temporal, binary, JSON, and engine-specific values into the target dialect. It sizes types around the keys and values that actually need to survive the move, normalizes identifiers where the target requires it, and makes unresolved mappings visible before they become bad data. The result is a target contract SQL Flow can apply, validate, and recover against. You get a destination that behaves as designed instead of discovering incompatibilities after the load has started.
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
SQL Flow uses the source, target, versions, types, keys, hosting model, and movement pattern to select the right path and surface compatibility risks before production work begins.
Talk through my use case