Supported databases

Burst Load moves a full dataset once with parallel, resumable bulk movement. Change Data Capture keeps a target current by applying committed inserts, updates, and deletes. SQL Flow can run either capability independently or coordinate a parallel seed with a pinned CDC handoff.

The shared SQL Flow catalog currently presents 49 source and target engines, including operational databases, cloud warehouses, lakes, and file formats. The exact source and target capabilities are shown on the supported databases page.

SQL Flow captures from Oracle, SQL Server and Azure SQL, PostgreSQL, MySQL, and Sybase ASE. DirectLog is the high-performance choice when source files or devices are reachable. Native streams and SQL-based readers cover environments with different access constraints.

Nothing is installed inside the database. The agent runs on nearby or separate compute. PostgreSQL pgoutput, MySQL binlog, SQL Server native CDC, Oracle LogMiner, and Sybase reconstruction use database or replication connections. DirectLog can leave only a tiny read-only broker beside the source while decode and apply run elsewhere. Managed-cloud availability still depends on what each provider exposes.

Every read has a cost, but the cost changes by mode. Direct file and device readers move parsing, transaction assembly, spooling, and apply off the database engine, though log reads still consume storage or network I/O. PostgreSQL and MySQL use native push streams. SQL mining and polling ask the source to do more work, with Oracle LogMiner as the clearest example. Choose the mode against the source’s actual performance budget.

Yes. Burst Load slices tables across parallel workers and can distribute work across agent machines. CDC can run multiple source pipelines and fan one captured stream out to multiple sinks. Every sink advances on an independent durable cursor, so one paused destination does not pause the others.

The agent runs in infrastructure you control on Windows or Linux. It initiates control traffic outbound, resolves connection secrets locally, and sends captured rows directly to your destinations. The control plane does not connect to your databases or receive the row stream. TLS is required by default for control traffic unless an operator deliberately enables an insecure development posture.

Eleven shipped sink connectors: PostgreSQL, MySQL, SQL Server, Azure SQL, Oracle, Sybase ASE, CockroachDB, Google Cloud Spanner, Apache Kafka, Google Pub/Sub, and Microsoft Fabric Open Mirroring.

Start with what the hosting model can expose. If logs are reachable, evaluate DirectLog first for high-performance off-box parsing. If they are not, compare the native stream or SQL-based reader by source work, required privileges, before-image behavior, schema scope, and measured throughput boundary.