Google Cloud SQL to Metabase Integration

How Datrise loads Google Cloud SQL into Metabase

Datrise syncs Google Cloud SQL's tables, rows, schemas, indexes, read replicas, and binlog changes into Metabase as clean SQL tables Metabase auto-discovers. Flexible or custom fields land in flattened columns for the question builder, and timestamps such as created, updated, and status changes are typed as temporal columns for trends.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for large questions. Metabase auto-scans schemas, so Datrise uses readable table and column names so the no-code UI stays self-explanatory.

Ideal for self-serve questions and dashboards for whole teams.

Endpoints

Google Cloud SQL: Managed MySQL, PostgreSQL, and SQL Server instances on GCP.

Metabase: Open-source analytics with questions, dashboards, and embedded insights.

How Google Cloud SQL entities map to Metabase

Google Cloud SQL entity	Metabase object	Notes
tables	`google_cloud_sql_tables`	id PK · custom fields → flattened columns for the question builder
rows	`google_cloud_sql_rows`	id PK · linked to google_cloud_sql_tables
schemas	`google_cloud_sql_schemas`	id PK · linked to google_cloud_sql_tables
indexes	`google_cloud_sql_indexes`	id PK · linked to google_cloud_sql_tables

FAQ

How does Datrise handle Google Cloud SQL's custom fields in Metabase?

Flexible values are stored as flattened columns for the question builder, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Metabase types.

How does the Google Cloud SQL to Metabase sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the connected tables.

Related pipelines

Early access

Connect Google Cloud SQL to Metabase the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.