Real-time
Two-way sync
Changes in Exasol or SAP Hana instantly reflect in both systems. No stale data, no manual imports.
Data warehouse ⇄ Database
Exasol to SAP Hana integration — real-time, two-way sync
Keep Exasol 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 Exasol and SAP Hana
Connect SAP Hana and Exasol 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 SAP Hana's rows in Exasol, 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 SAP Hana where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in SAP Hana sync into Exasol in real time, and result tables in Exasol sync back into SAP Hana, with schema and type mapping between the two systems handled for you.
Common use cases
- 01 Keep dimension tables such as customers and products aligned with the systems of record.
- 02 Load CRM and ERP records into Exasol tables on a schedule so analysts query fresh operational data.
- 03 Read SYS.TABLES and TABLE_COLUMNS system views to auto-discover schema and generate field mappings when new tables are added to the sync.
- 04 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.
Common sync patterns
Fresh analytics without loading windows
Because changes stream continuously, analysts query current data instead of waiting for last night's load.
Offload heavy reads
Point analytical queries at the synced copy in Exasol and keep SAP Hana focused on its operational workload.
Operational data in the warehouse, minus the pipeline
Rows from SAP Hana land in Exasol as they change, replacing hand-built CDC and batch extract jobs.
What you can sync between Exasol 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.
| Exasol objects | SAP Hana objects | How this pairing syncs | |
|---|---|---|---|
| Schemas Namespaces that group the tables a sync reads from or writes into. | Schemas Namespaces that group tables and views; the connector targets a schema and enumerates its objects from the catalog to build the sync. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| UDF scripts In-database functions that can transform synced data after load. | 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. | UDF scripts is specific to Exasol and Row store tables to SAP Hana — each maps to any object or custom field on the other side. | |
| Users and roles Grant read/write access for the dedicated integration account. | Calculation views Modeled analytic views over base tables; read-only sources for pushing aggregated or joined results into a warehouse or downstream app. | Users and roles is specific to Exasol and Calculation views to SAP Hana — each maps to any object or custom field on the other side. | |
| Tables Primary sync target; columnar relational tables written with standard SQL. | 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 Exasol and SQL views to SAP Hana — each maps to any object or custom field on the other side. | |
| Views Read-only query surfaces often used as curated sources for reverse ETL. | Sequences Server-generated key values; relevant when writing rows into tables whose identity is assigned HANA-side rather than by the source system. | Views is specific to Exasol and Sequences to SAP Hana — each maps to any object or custom field on the other side. | |
| Virtual schemas Federated views over external sources; useful for deciding what needs physical replication. | 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. | Virtual schemas is specific to Exasol and Triggers to SAP Hana — each maps to any object or custom field on the other side. |
How changes propagate between Exasol 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.
Exasol SAP Hana Interval-based propagation
DetectionStacksync polls Exasol for changes on an incremental schedule, reading only records changed since the previous pass. Polling with timestamp or key columns.
DeliveryEach detected change is applied to SAP Hana as a row-level write, with types converted between the two schemas.
SAP Hana Exasol 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 Exasol as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Exasol: No API quota; concurrency is bounded by cluster resources and session limits.
- 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 Exasol ⇄ SAP Hana
Connect Exasol and SAP Hana for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Exasol–SAP Hana connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Exasol 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 Exasol or SAP Hana record.
Observability
Monitoring
Track your Exasol ⇄ 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 Exasol and SAP Hana.
How the Exasol and SAP Hana connectors work
Exasol
- Integration surface
- SQL over JDBC/ODBC drivers and a WebSocket-based client protocol
- Authentication
- Database credentials (username and password)
- Change detection
- Polling with timestamp or key columns; Exasol does not expose a transaction-log change feed to clients
- Capabilities
- read · write
- Rate limits
- No API quota; concurrency is bounded by cluster resources and session limits
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 Exasol 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.
- 01
Connect your apps
Authenticate Exasol 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.
Exasol
connected
SAP Hana
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Exasol 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.
objects · Exasol ⇄ SAP HanaCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Exasol SAP HanaCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Exasol and SAP Hana integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Exasol and SAP Hana: authenticate both systems, choose the objects to sync (such as Exasol's Schemas and UDF scripts), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Exasol: Virtual schemas let Exasol query external sources in place, which affects whether data needs to be physically synced at all. SAP Hana: Tables need a primary key for reliable upserts and delete tracking; keyless tables require a synthetic key or full-table comparison. Stacksync's field mapping accounts for these differences between Exasol and SAP Hana without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Exasol and SAP Hana records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Exasol and SAP Hana connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Exasol–SAP Hana integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Exasol and SAP Hana. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Exasol: Polling with timestamp or key columns; Exasol does not expose a transaction-log change feed to clients. On SAP Hana: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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.
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 466 integrations available for Exasol and SAP Hana.
Popular · 4 of 466
No integrations match .
