Connection Setup
Before reading changes, set up your Google Cloud SQL connection. See Connecting to Google Cloud SQL for MySQL for the credentials and network access required. Once the connection exists, add the Google Cloud SQL (Snapshot CDC) source component to your pipeline and select it.Snapshot Storage
Google Cloud SQL Snapshot CDC uses File Based snapshot storage. The snapshot of your previous run is stored as a Parquet file on Integrate.io managed cloud storage, which means:- Only read access to your Cloud SQL database is required.
- No snapshot tables are created in your source database.
- On the first run, every current record is treated as upserted because there is no previous snapshot to compare against.
Database (table-based) snapshot storage is only available for SQL Server connections. For Google Cloud SQL, File Based storage is the only option, and you do not need to configure an S3 connection of your own.
Change Detection
Choose how the component decides whether a row has changed:- Primary Key: matches rows by a unique identifier column and detects updates by comparing the remaining column values. Best when the table has a reliable key.
- Composite Hash: builds a hash from all or selected columns and compares hashes between runs. Best when the table has no reliable primary key.
Full Configuration Reference
Snapshot CDC Source reference
Configuration steps, change detection methods, query mode, best practices, troubleshooting, and limitations that apply to every Snapshot CDC source.