Skip to content
Replication route

MySQL to Snowflake
real-time replication

TwinCommit replicates MySQL to Snowflake in real time by reading the MySQL transaction log and applying every committed change exactly once and in commit order. Use it to feed Snowflake with live MySQL data for analytics, AI and reporting, with no triggers or capture tables on the source.

MySQL

log reader

commit-ordered · exactly-once

Snowflake

native writer

How capture works on MySQL

TwinCommit connects as a replica, reads the row-based binary log and tracks position by GTID, so failovers and replica promotions are seamless.

Prerequisites

  • ✓binlog_format = ROW and binlog_row_image = FULL
  • ✓GTID mode recommended
  • ✓REPLICATION SLAVE and REPLICATION CLIENT grants
MySQL source docs →

How apply works on Snowflake

Rows land through Snowpipe Streaming into a change table and are merged into the target on a short, configurable interval.

Requirements

  • ✓Key-pair authentication for a service user
  • ✓A warehouse for the MERGE step
  • ✓OWNERSHIP or INSERT/UPDATE/DELETE on the target schema
Snowflake target docs →

Setup

Set up MySQL → Snowflake in four steps

  1. 1

    Prepare MySQL

    Run twincommit check. It verifies binlog_format = row and binlog_row_image = full and the other prerequisites, and prints the exact fix for anything missing.

  2. 2

    Point at Snowflake

    Add a target block for Snowflake. TwinCommit can generate target DDL with twincommit ddl -apply.

  3. 3

    Snapshot

    twincommit snapshot copies each table under a brief share lock and records the exact log position.

  4. 4

    Stream

    twincommit run streams every committed change from that position, exactly once and in commit order.

pipelines/mysql-to-snowflake.yaml
source:
  type: mysql
  dsn: ${SOURCE_DSN}
  server_id: 4201

target:
  type: snowflake
  account: myorg-myaccount
  warehouse: REPLICATION_WH
  database: RAW
  private_key_file: /secrets/sf.p8

tables:
  - source: SALES.ORDERS
  - source: SALES.ORDER_LINES
    exclude_columns: [INTERNAL_NOTES]

MySQL to Snowflake replication FAQ

How does TwinCommit replicate MySQL to Snowflake?

+

TwinCommit reads changes from the MySQL transaction log, buffers them per transaction, and applies each committed transaction to Snowflake in commit order. Rows land through Snowpipe Streaming into a change table and are merged into the target on a short, configurable interval.

Does MySQL to Snowflake replication need triggers or capture tables?

+

No. TwinCommit reads the MySQL log directly and creates no objects in the source database.

Is MySQL to Snowflake replication exactly-once?

+

Yes. TwinCommit commits its checkpoint in the same Snowflake transaction as the data, so a crash or restart never loses or duplicates a transaction.

What MySQL versions are supported?

+

MySQL 5.7, 8.0, 8.4, 9.x · Amazon RDS & Aurora MySQL · Azure Database for MySQL · Cloud SQL.

Stream MySQL to Snowflake today.

Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.