Skip to content
Data warehouse ⇄ Database

Dremio to Google Cloud Spanner integration — real-time, two-way sync

Keep Dremio and Google Cloud Spanner in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from Mulesoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Dremio and Google Cloud Spanner

Connect Google Cloud Spanner and Dremio with one live, two-way sync: operational rows flow into the warehouse, and computed results flow back where systems can read them fast.

Operational databases and analytical warehouses want the same data at different moments. Analysts want Google Cloud Spanner's rows in Dremio, current and joinable, without a change-data-capture pipeline to maintain. Engineers want the outputs of warehouse work, such as aggregates, features, and segments, available in Google Cloud Spanner where the services that read from it get them at normal query latency.

Stacksync covers both directions with one connection. Tables or collections in Google Cloud Spanner sync into Dremio in real time, and result tables in Dremio sync back into Google Cloud Spanner, with schema and type mapping between the two systems handled for you.

Common use cases

  • Consolidate data from multiple lake sources through one Dremio semantic layer into a single warehouse target.
  • Sync curated Dremio views into an operational Postgres so applications get low-latency access to lakehouse data.
  • Run a two-way sync between Spanner and a SaaS tool so edits made by ops teams land back in the application database.
  • Consolidate data from a globally distributed Spanner deployment into regional business systems.

Offload heavy reads

Point analytical queries at the synced copy in Dremio and keep Google Cloud Spanner focused on its operational workload.

Operational data in the warehouse, minus the pipeline

Rows from Google Cloud Spanner land in Dremio as they change, replacing hand-built CDC and batch extract jobs.

Serve warehouse results at database speed

Aggregates or model outputs computed in Dremio sync into Google Cloud Spanner, where whatever reads from that database gets them without querying the warehouse.

What you can sync between Dremio and Google Cloud Spanner

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Dremio objects Google Cloud Spanner objects
Reflections Materialized accelerations that make repeated extraction queries cheaper. Rows The unit of read and write in each sync cycle, keyed by primary key.
Jobs Query execution records useful for monitoring sync workloads. Interleaved tables Child rows physically co-located with parents; synced as related records.
Sources Connected storage and database systems (S3, ADLS, relational databases) Dremio queries in place. Secondary indexes Used to make incremental read queries efficient on non-key columns.
Physical datasets Tables and files promoted from sources; the raw data a sync ultimately reads. Change streams Capture inserts, updates, and deletes for log-style change data capture.
Virtual datasets (views) SQL views layering semantics over physical data; the preferred sync target for curated extracts. Views Read-only projections useful for shaping data before it leaves Spanner.
Apache Iceberg tables Lakehouse tables supporting DML and snapshot metadata usable for incremental reads. Databases Top-level containers that scope schema and sync configuration.
What ships with Dremio ⇄ Google Cloud Spanner

Connect Dremio and Google Cloud Spanner for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dremio–Google Cloud Spanner connection.

Real-time

Two-way sync

Changes in Dremio or Google Cloud Spanner instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Dremio or Google Cloud Spanner data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Dremio or Google Cloud Spanner record.

Observability

Monitoring

Track your Dremio ⇄ Google Cloud Spanner sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Dremio and Google Cloud Spanner.

How the Dremio and Google Cloud Spanner connectors work

Dremio

Integration surface
Arrow Flight SQL, JDBC/ODBC, and a REST API
Authentication
Personal access tokens or username/password; OAuth-based SSO on Dremio Cloud
Change detection
Polling via SQL; Iceberg table snapshots can anchor incremental reads; no consumer-facing change feed
Capabilities
read · write
Rate limits
Bounded by engine capacity and workload management rather than API rate limits

Google Cloud Spanner

Integration surface
gRPC/REST client API with SQL query surface (GoogleSQL and PostgreSQL-interface dialects)
Authentication
Google Cloud IAM (service accounts)
Change detection
Change streams (log-style CDC), or timestamp-based polling queries
Capabilities
read · write · CDC
Rate limits
Throughput is bounded by the instance's provisioned compute capacity rather than a fixed API quota.
How it works

How to connect Dremio to Google Cloud Spanner — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Dremio and Google Cloud Spanner with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Dremio connected
    Google Cloud Spanner connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Dremio and Google Cloud Spanner objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Dremio ⇄ Google Cloud Spanner
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Dremio Google Cloud Spanner
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Dremio and Google Cloud Spanner integration FAQ

SECURITY

Security teams love Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 386 integrations available for Dremio and Google Cloud Spanner.

Popular · 8 of 386
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.