MySQL Connector

Extract MySQL tables with full refresh or cursor-based incremental sync. Uses database credentials and optional lookback for late-arriving rows.

SourceCommunity

Start Free View Documentation

Evaluating against Fivetran? See how Supaflow handles MySQL pricing, connector quality, and Snowflake deployment side-by-side.

Supaflow vs Fivetran

Why Supaflow

All connectors included

Every connector is available on every plan. Pricing does not increase with connector count.

Pay for compute, not rows

Credit-based pricing. Usage scales with your pipelines, not with row counts.

One platform

Ingestion, dbt Core transformation, reverse ETL, and orchestration in a single workspace.

Capabilities

Full Refresh and Incremental Sync

Use full refresh for smaller or static tables, or cursor-based incremental sync for tables with reliable date, datetime, or timestamp columns. The connector does not use binary log CDC.

Read-Only Database Access

Connect with a dedicated MySQL user and grant SELECT only on the database or tables you want Supaflow to read.

Single-Database Scope

Each source connection targets one MySQL database. Create separate sources when you need to sync tables from multiple MySQL databases.

Incremental Lookback Window

Configure a lookback period up to 24 hours so incremental syncs re-read a short window before the previous cursor position when writes can arrive out of order.

Supported Objects

Database Objects

Tables

Tables in the configured MySQL database that the connecting user has SELECT permission on.

How It Works

Prepare MySQL access

Create a dedicated read-only user with SELECT privileges on the tables you want to sync. If your database restricts inbound access, allow Supaflow IP 18.214.240.61 or use your approved private network path.

Enter connection details

Provide the MySQL host, port (default 3306), database name, username, and password.

Choose sync behavior

Select tables in your pipeline and use full refresh or cursor-based incremental sync. For incremental sync, choose a cursor column that advances when rows are inserted or updated.

Test and save

Click Test & Save to verify the connection. Supaflow discovers accessible tables and refreshes metadata according to the schema refresh interval.

Use Cases

MySQL analytics replication

Sync operational MySQL tables into your warehouse for analytics without running heavy reporting queries against production.

Service database consolidation

Create separate MySQL sources for service-owned databases and load selected tables into one analytics environment.

Incremental warehouse updates

Use cursor-based incremental sync for large tables that have reliable updated-at style columns.

Frequently Asked Questions

Does the MySQL connector support CDC or binary log replication?

No. The MySQL connector supports full refresh and cursor-based incremental sync. It does not read the binary log and does not detect hard deletes from the source.

Can one source sync multiple MySQL databases?

No. Each MySQL source is configured for one database. Create another source for each additional database you want to sync.

Can I sync MySQL views?

The current connector discovers tables in the configured database. Views are not exposed as supported objects on this source page.

Do I need to whitelist an IP address?

If your MySQL server restricts inbound connections, allow Supaflow IP 18.214.240.61 or connect through your approved private network path.

Can I configure client certificates or SSL mode?

The current MySQL source configuration does not expose client certificate or SSL-mode fields. Use an approved private network path or contact support if your database requires those settings.

What happens with late-arriving updates?

Use the optional lookback period to re-read a short window before the previous cursor position. This can capture rows written slightly out of order, but the cursor column still needs to be reliable.