Real-time
Two-way sync
Changes in SAP Hana or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Data warehouse
SAP Hana to Starburst Enterprise integration — real-time, two-way sync
Keep SAP Hana and Starburst Enterprise 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 Starburst Enterprise
Connect SAP Hana and Starburst Enterprise 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 Starburst Enterprise, 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 Starburst Enterprise in real time, and result tables in Starburst Enterprise sync back into SAP Hana, with schema and type mapping between the two systems handled for you.
Common use cases
- 01 Expose Iceberg or Hive lake tables to sync jobs through one SQL endpoint without moving the data first
- 02 Consolidate reads from multiple databases behind a single connection instead of maintaining one integration per source
- 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
Offload heavy reads
Point analytical queries at the synced copy in Starburst Enterprise and keep SAP Hana focused on its operational workload.
Operational data in the warehouse, minus the pipeline
Rows from SAP Hana land in Starburst Enterprise as they change, replacing hand-built CDC and batch extract jobs.
Serve warehouse results at database speed
Aggregates or model outputs computed in Starburst Enterprise sync into SAP Hana, where whatever reads from that database gets them without querying the warehouse.
What you can sync between SAP Hana and Starburst Enterprise
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 | Starburst Enterprise 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 Namespaces within a catalog, mirroring the underlying source's databases or schemas. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| 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. | Materialized views Precomputed results that make repeated sync reads cheaper. | Triggers is specific to SAP Hana and Materialized views to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| 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. | Columns Typed per the Trino type system, mapped from each source's native types. | System-versioned temporal tables is specific to SAP Hana and Columns to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| 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. | Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. | System views (SYS schema) is specific to SAP Hana and Catalogs to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| 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. | Tables Queryable relations; writes pass through to sources whose connectors support them. | Column store tables is specific to SAP Hana and Tables to Starburst Enterprise — 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. | Views Engine-level SQL views used to shape federated data before syncing it out. | Row store tables is specific to SAP Hana and Views to Starburst Enterprise — each maps to any object or custom field on the other side. |
How changes propagate between SAP Hana and Starburst Enterprise
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 Starburst Enterprise 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 Starburst Enterprise as a row-level write, with types converted between the two schemas.
Starburst Enterprise SAP Hana Interval-based propagation
DetectionStacksync polls Starburst Enterprise for changes on an incremental schedule, reading only records changed since the previous pass. Query-based polling.
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.
- Starburst Enterprise: Throughput is governed by cluster sizing and resource groups rather than API quotas.
What ships with SAP Hana ⇄ Starburst Enterprise
Connect SAP Hana and Starburst Enterprise for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every SAP Hana–Starburst Enterprise connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever SAP Hana or Starburst Enterprise 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 Starburst Enterprise record.
Observability
Monitoring
Track your SAP Hana ⇄ Starburst Enterprise 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 Starburst Enterprise.
How the SAP Hana and Starburst Enterprise 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.
Starburst Enterprise
- Integration surface
- ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol
- Authentication
- Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos
- Change detection
- Query-based polling; Starburst is a query engine and exposes no change log of its own
- Capabilities
- read · write
- Rate limits
- Throughput is governed by cluster sizing and resource groups rather than API quotas
How it works
How to connect SAP Hana to Starburst Enterprise — 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 SAP Hana and Starburst Enterprise with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
SAP Hana
connected
Starburst Enterprise
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the SAP Hana and Starburst Enterprise 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 · SAP Hana ⇄ Starburst EnterpriseCustomers 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.
SAP Hana Starburst EnterpriseCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
SAP Hana and Starburst Enterprise integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between SAP Hana and Starburst Enterprise: authenticate both systems, choose the objects to sync (such as SAP Hana's Schemas and Triggers), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Starburst Enterprise: The engine stores no data itself; reads and writes pass through to the underlying sources, and write support depends on each connector. SAP Hana: Connections are governed by workload classes and admission control, so heavy sync concurrency competes with production query load and can be throttled by memory and thread caps. Stacksync's field mapping accounts for these differences between SAP Hana and Starburst Enterprise 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 SAP Hana and Starburst Enterprise records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed SAP Hana and Starburst Enterprise connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom SAP Hana–Starburst Enterprise integration in-house.
-
Yes — Stacksync ships production-grade connectors for both SAP Hana and Starburst Enterprise. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection 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. On Starburst Enterprise: Query-based polling; Starburst is a query engine and exposes no change log of its own. 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 470 integrations available for SAP Hana and Starburst Enterprise.
Popular · 4 of 470
No integrations match .
