Skip to content
Database

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

Keep Google Cloud Spanner and SAP Hana 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 Google Cloud Spanner and SAP Hana

Keep Google Cloud Spanner and SAP Hana synchronized in real time, across engines, regions, or services, in one or both directions.

Two databases that must agree is one of the oldest problems in engineering: different engines for different workloads, separate services with overlapping reference data, a migration in flight, or regional instances that share a subset of records. Hand-rolled replication across systems means change capture, conflict handling, and type mapping, all built and maintained by your team.

Stacksync syncs tables or collections between Google Cloud Spanner and SAP Hana continuously and bi-directionally, translating types between the two engines and resolving conflicts by rules you configure. Rows written on either side appear on the other within seconds.

Common use cases

  • 01 Use change streams to feed near-real-time copies of operational tables into an analytics warehouse.
  • 02 Run a two-way sync between Spanner and a SaaS tool so edits made by ops teams land back in the application database.
  • 03 Detect inserts, updates, and deletes on high-write tables via AFTER triggers or a last-modified column and replicate the deltas downstream near-real-time.
  • 04 Read SYS.TABLES and TABLE_COLUMNS system views to auto-discover schema and generate field mappings when new tables are added to the sync.

Common sync patterns

Cross-engine sync

Keep the same dataset live in both Google Cloud Spanner and SAP Hana, so each workload runs on the engine that suits it.

Migration with zero-downtime cutover

When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.

Shared reference data between services

Services that own separate databases stay consistent on the records they share, without a custom replication layer.

What you can sync between Google Cloud Spanner and SAP Hana

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.

Google Cloud Spanner objects SAP Hana objects How this pairing syncs
Tables Relational tables mapped one-to-one to sync targets. SQL views Standard database views; read-only projections synced outbound when the source data should not be exposed as raw base tables. Tables is specific to Google Cloud Spanner and SQL views to SAP Hana — each maps to any object or custom field on the other side.
Rows The unit of read and write in each sync cycle, keyed by primary key. Schemas Namespaces that group tables and views; the connector targets a schema and enumerates its objects from the catalog to build the sync. Rows is specific to Google Cloud Spanner and Schemas to SAP Hana — each maps to any object or custom field on the other side.
Interleaved tables Child rows physically co-located with parents; synced as related records. Sequences Server-generated key values; relevant when writing rows into tables whose identity is assigned HANA-side rather than by the source system. Interleaved tables is specific to Google Cloud Spanner and Sequences to SAP Hana — each maps to any object or custom field on the other side.
Secondary indexes Used to make incremental read queries efficient on non-key columns. Triggers AFTER INSERT/UPDATE/DELETE triggers capture changes into a shadow/logging table so updates and deletes are detected near-real-time without full scans. Secondary indexes is specific to Google Cloud Spanner and Triggers to SAP Hana — each maps to any object or custom field on the other side.
Change streams Capture inserts, updates, and deletes for log-style change data capture. System-versioned temporal tables Column store tables with a history table tracking each row's validity period; used to reconstruct update and delete history for change capture. Change streams is specific to Google Cloud Spanner and System-versioned temporal tables to SAP Hana — each maps to any object or custom field on the other side.
Views Read-only projections useful for shaping data before it leaves Spanner. System views (SYS schema) Catalog and monitoring views such as SYS.TABLES and TABLE_COLUMNS; read to discover schema and auto-generate field mappings for new tables. Views is specific to Google Cloud Spanner and System views (SYS schema) to SAP Hana — each maps to any object or custom field on the other side.

How changes propagate between Google Cloud Spanner and SAP Hana

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Google Cloud Spanner SAP Hana Sub-second propagation

DetectionChanges in Google Cloud Spanner are captured at the source via change data capture — no polling loop against its API. Change streams (log-style CDC), or timestamp-based polling queries.

DeliveryEach detected change is applied to SAP Hana as a row-level write, with types converted between the two schemas.

SAP Hana Google Cloud Spanner Sub-second propagation

DetectionChanges in SAP Hana are captured at the source via change data capture — no polling loop against its API. Polling on a last-modified timestamp column, or AFTER INSERT/UPDATE/DELETE triggers writing to a shadow table.

DeliveryEach detected change is applied to Google Cloud Spanner as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Google Cloud Spanner: Throughput is bounded by the instance's provisioned compute capacity rather than a fixed API quota.
  • SAP Hana: No SaaS-style request quota; throughput is bounded by connection limits, statement memory caps, and workload-class admission control (concurrency/memory limits) that share capacity with production queries.
What ships with Google Cloud Spanner ⇄ SAP Hana

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Google Cloud Spanner or SAP Hana 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 Google Cloud Spanner or SAP Hana record.

Observability

Monitoring

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

Trading partners

EDI

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

How the Google Cloud Spanner and SAP Hana connectors work

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.

SAP Hana

Integration surface
SQL over the SAP HANA client (JDBC/ODBC drivers); OData/REST via XS for app-layer access
Authentication
Dedicated database user credentials over an encrypted TLS connection (password sent hashed); Kerberos, SAML, JWT, and X.509 certificate authentication are also supported. SAP HANA Cloud enforces TLS and IP allowlisting.
Change detection
Polling on a last-modified timestamp column, or AFTER INSERT/UPDATE/DELETE triggers writing to a shadow table; system-versioned temporal tables and SLT/SDI provide trigger- and log-based CDC. No native webhooks.
Capabilities
read · write · CDC
Rate limits
No SaaS-style request quota; throughput is bounded by connection limits, statement memory caps, and workload-class admission control (concurrency/memory limits) that share capacity with production queries.
How it works

How to connect Google Cloud Spanner to SAP Hana — 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 Google Cloud Spanner and SAP Hana 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
    Google Cloud Spanner connected
    SAP Hana connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Google Cloud Spanner and SAP Hana 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 · Google Cloud Spanner ⇄ SAP Hana
    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
    Google Cloud Spanner SAP Hana
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Google Cloud Spanner and SAP Hana integration FAQ

SECURITY

Security teams trust 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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

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

Popular · 7 of 461
All Google Cloud Spanner integrations All SAP Hana integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own