Source connector

Google Cloud SQL connector

Google Cloud SQL integration for databases, warehouses and BI tools

Managed MySQL, PostgreSQL, and SQL Server instances on GCP. Datrise captures Google Cloud SQL entities such as tables, rows, schemas, indexes, read replicas and binlog changes, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Cloud SQL for MySQL / PostgreSQL native replication (binlog / logical decoding) + Cloud SQL Admin API v1 authenticates with username / password, service account, mTLS, incremental runs key on binlog GTID/position (MySQL) or WAL LSN via replication slot (PostgreSQL).

Of the 6 objects, 5 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `google_cloud_sql_tables`) with a schema derived from the Google Cloud SQL API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Google Cloud SQL pipeline page, and join the waitlist to get the Google Cloud SQL connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Google Cloud SQL data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
tables	google_cloud_sql_tables	Upsert by primary key, incremental on updated-at
rows	google_cloud_sql_rows	Upsert by primary key, incremental on updated-at
schemas	google_cloud_sql_schemas	Upsert by primary key, incremental on updated-at
indexes	google_cloud_sql_indexes	Upsert by primary key, incremental on updated-at
read replicas	google_cloud_sql_read_replicas	Upsert by primary key, incremental on updated-at
binlog changes	google_cloud_sql_binlog_changes	Append-only, incremental by timestamp

Google Cloud SQL API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Cloud SQL for MySQL / PostgreSQL native replication (binlog / logical decoding) + Cloud SQL Admin API v1
Authentication	username / password, service account, mTLS — Connects over the native MySQL/PostgreSQL wire protocol with a database username/password, or through the Cloud SQL Auth Proxy, which pulls an ephemeral mTLS certificate from the Cloud SQL Admin API and can layer on automatic IAM database authentication (short-lived OAuth 2.0 access tokens) instead of a password.
Pagination	keyset — MySQL CDC reads a forward-only binary-log position/GTID stream; PostgreSQL logical replication reads a forward-only WAL LSN stream via a replication slot — both are continuous log tails, not page-based result sets.
Rate limit	Not published
Incremental cursor	binlog GTID/position (MySQL) or WAL LSN via replication slot (PostgreSQL) — Cloud SQL publishes no queries-per-second limit for either engine; the practical ceiling for change-stream throughput is the instance's machine tier and `max_connections`/`max_replication_slots`.
Webhooks	No
Bulk export	Yes — Cloud SQL Admin API `instances.export` (SQL dump or CSV to Cloud Storage)
Deletes detectable	Yes — MySQL: DELETE row events in the binlog when `binlog_row_image=FULL`; PostgreSQL: DELETE messages from the logical replication stream, with old-row values available when `REPLICA IDENTITY FULL` is set

Official API reference

What bites when replicating Google Cloud SQL

Enabling MySQL CDC requires three instance flags — `log_bin` on, `binlog_format=ROW`, `binlog_row_image=FULL` — and binary logs default to 7 days of retention (`binlog_expire_logs_seconds`), so a connector down longer than that loses its resume position and needs a fresh snapshot.
PostgreSQL logical replication needs the Cloud SQL-specific `cloudsql.logical_decoding` flag turned on (it sets `wal_level=logical` for you) plus a `REPLICATION`-privileged user; `max_replication_slots` defaults to 10 and scales only 2-8 slots per GB of instance memory, so several concurrent connectors can exhaust the slot pool on a small instance.
Cloud SQL for MySQL publishes no queries-per-second limit, but `CREATE SUBSCRIPTION` on PostgreSQL and `pglogical` both require the `cloudsqlsuperuser` role, which a least-privilege replication user typically doesn't have by default.
Automatic IAM database authentication issues OAuth 2.0 access tokens valid for only 1 hour, so a long-running extraction through the Cloud SQL connector must refresh its token mid-run instead of authenticating once at startup.

Compare this against every other documented API

Popular destinations for Google Cloud SQL

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Google Cloud SQL connector FAQ

What Google Cloud SQL data does the connector extract?: 6 objects: tables, rows, schemas, indexes, read replicas and binlog changes. Each lands in its own table with types preserved; history-style objects (1: binlog changes) load as append-only streams.
Is the Google Cloud SQL integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Google Cloud SQL data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Google Cloud SQL → destination pair has its own page with the object-to-table mapping.

Related sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Google Cloud SQL pipeline with guided onboarding

Join the waitlist to get priority access for Google Cloud SQL integrations with guided setup, schema-aware mapping, and production-grade incremental sync.