Compatibility and data types

A database logo is not enough. Check the exact capability and contract.

Burst Load source and target roles, CDC modes, hosting, log access, recovery, replica identity, supplemental logging, keys, and apply profiles can all change behavior.

Talk through my use case Review CDC sources

Shared catalog

Start with the engine roles the product actually exposes.

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

Know what each reader emits.

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 payoff

See what the capability changes.

Catalog

Engine roles

Confirm Burst Load and CDC capabilities from one source.

Mode

Prerequisites

Validate the exact capture or loading interface.

Type

Explicit fidelity

Preserve values or surface a visible incompatibility.

Where the work happens

The details that make the result usable.

Target contract

Validate mappings before loading or applying.

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.

Take the next step

Check the exact path before committing.

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