Skip to content
Database

SAP Hana to TimescaleDB integration — real-time, two-way sync

Keep SAP Hana and TimescaleDB 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 SAP Hana and TimescaleDB

Keep SAP Hana and TimescaleDB 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 SAP Hana and TimescaleDB 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 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.
  • 02 Read SYS.TABLES and TABLE_COLUMNS system views to auto-discover schema and generate field mappings when new tables are added to the sync.
  • 03 Keep device or asset reference tables bi-directionally in sync between TimescaleDB and an ERP.
  • 04 Consolidate metrics from several services into one hypertable to serve a single reporting layer.

Common sync patterns

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.

Regional or environment copies

Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.

What you can sync between SAP Hana and TimescaleDB

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.

SAP Hana objects TimescaleDB objects How this pairing syncs
Schemas Namespaces that group tables and views; the connector targets a schema and enumerates its objects from the catalog to build the sync. Schemas Postgres namespaces used to separate synced datasets by team or environment. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Column store tables HANA's default table type, optimized for analytics; synced two-way as rows over the SQL interface with the primary key driving upserts and delete tracking. Chunks Time-bounded partitions of a hypertable; syncs read and write through the parent hypertable and never address chunks directly. Column store tables is specific to SAP Hana and Chunks to TimescaleDB — each maps to any object or custom field on the other side.
Row store tables OLTP-oriented tables held fully in memory; read and written the same way through the SAP HANA client for high-write operational tables. Continuous Aggregates Incrementally maintained rollups that serve as pre-aggregated read sources for downstream systems. Row store tables is specific to SAP Hana and Continuous Aggregates to TimescaleDB — each maps to any object or custom field on the other side.
Calculation views Modeled analytic views over base tables; read-only sources for pushing aggregated or joined results into a warehouse or downstream app. Regular PostgreSQL Tables Relational reference data such as devices, tenants, or accounts synced alongside the series data. Calculation views is specific to SAP Hana and Regular PostgreSQL Tables to TimescaleDB — each maps to any object or custom field on the other side.
SQL views Standard database views; read-only projections synced outbound when the source data should not be exposed as raw base tables. Views Standard SQL views used to shape or filter data for consumers. SQL views is specific to SAP Hana and Views to TimescaleDB — each maps to any object or custom field on the other side.
Sequences Server-generated key values; relevant when writing rows into tables whose identity is assigned HANA-side rather than by the source system. Hypertables Time-partitioned tables that hold the main time-series data; the primary read and write target in syncs. Sequences is specific to SAP Hana and Hypertables to TimescaleDB — each maps to any object or custom field on the other side.

How changes propagate between SAP Hana and TimescaleDB

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.

SAP Hana TimescaleDB 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 TimescaleDB as a row-level write, with types converted between the two schemas.

TimescaleDB SAP Hana Sub-second propagation

DetectionChanges in TimescaleDB are captured at the source via change data capture — no polling loop against its API. Log-based capture via PostgreSQL logical decoding where the deployment allows it — hypertable changes surface on the underlying chunk tables and must.

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

Rate-limit considerations

  • 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.
  • TimescaleDB: No API rate limits; throughput is bounded by database resources and connection limits.
What ships with SAP Hana ⇄ TimescaleDB

Connect SAP Hana and TimescaleDB for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between SAP Hana and TimescaleDB.

How the SAP Hana and TimescaleDB connectors work

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.

TimescaleDB

Integration surface
SQL wire protocol (PostgreSQL)
Authentication
Database credentials
Change detection
Log-based capture via PostgreSQL logical decoding where the deployment allows it — hypertable changes surface on the underlying chunk tables and must be remapped to the parent — or timestamp-based polling on time columns; regular Postgres tables replicate through standard logical replication
Capabilities
read · write · CDC
Rate limits
No API rate limits; throughput is bounded by database resources and connection limits.
How it works

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

    Choose tables

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

SAP Hana and TimescaleDB 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 463 integrations available for SAP Hana and TimescaleDB.

Popular · 6 of 463
All SAP Hana integrations All TimescaleDB 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