Two-way sync
Changes in Rockset or SAP Hana instantly reflect in both systems. No stale data, no manual imports.
Keep Rockset 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.
Operational databases and analytical warehouses want the same data at different moments. Analysts want SAP Hana's rows in Rockset, 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 Rockset in real time, and result tables in Rockset sync back into SAP Hana, with schema and type mapping between the two systems handled for you.
Aggregates or model outputs computed in Rockset sync into SAP Hana, where whatever reads from that database gets them without querying the warehouse.
Because changes stream continuously, analysts query current data instead of waiting for last night's load.
Point analytical queries at the synced copy in Rockset and keep SAP Hana focused on its operational workload.
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.
| Rockset objects | SAP Hana objects | How this pairing syncs | |
|---|---|---|---|
| Aliases Stable names that point at collections, used to swap datasets without changing queries. | 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. | Aliases is specific to Rockset and Row store tables to SAP Hana — each maps to any object or custom field on the other side. | |
| Integrations Managed source connections (databases, streams, object storage) feeding collections. | Calculation views Modeled analytic views over base tables; read-only sources for pushing aggregated or joined results into a warehouse or downstream app. | Integrations is specific to Rockset and Calculation views to SAP Hana — each maps to any object or custom field on the other side. | |
| Virtual Instances Isolated compute units that separate ingest from query workloads. | SQL views Standard database views; read-only projections synced outbound when the source data should not be exposed as raw base tables. | Virtual Instances is specific to Rockset and SQL views to SAP Hana — each maps to any object or custom field on the other side. | |
| Collections Schemaless document containers that ingested and synced records land in. | Schemas Namespaces that group tables and views; the connector targets a schema and enumerates its objects from the catalog to build the sync. | Collections is specific to Rockset and Schemas to SAP Hana — each maps to any object or custom field on the other side. | |
| Documents JSON records addressable by _id, written via the Write API in sync pipelines. | Sequences Server-generated key values; relevant when writing rows into tables whose identity is assigned HANA-side rather than by the source system. | Documents is specific to Rockset and Sequences to SAP Hana — each maps to any object or custom field on the other side. | |
| Workspaces Namespaces that group collections and query lambdas per team or environment. | 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. | Workspaces is specific to Rockset and Triggers to SAP Hana — each maps to any object or custom field on the other side. |
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.
DetectionStacksync polls Rockset for changes on an incremental schedule, reading only records changed since the previous pass. Polling via SQL queries on timestamp fields.
DeliveryEach detected change is applied to SAP Hana as a row-level write, with types converted between the two schemas.
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 Rockset as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Rockset–SAP Hana connection.
Changes in Rockset or SAP Hana instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Rockset or SAP Hana data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Rockset or SAP Hana record.
Track your Rockset ⇄ SAP Hana sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Rockset and SAP Hana.
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.
Authenticate Rockset 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.
Pick the Rockset 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Rockset and SAP Hana: authenticate both systems, choose the objects to sync (such as Rockset's Aliases and Integrations), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for Rockset and SAP Hana: Serve warehouse results at database speed; Fresh analytics without loading windows; Offload heavy reads. Aggregates or model outputs computed in Rockset sync into SAP Hana, where whatever reads from that database gets them without querying the warehouse.
Rockset: REST API (SQL over HTTP, plus a document Write API). Authentication: API key. SAP Hana: 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. Stacksync manages authentication, retries, and rate limits on both sides.
Rockset: Rockset was acquired by OpenAI in 2024 and the public service was subsequently wound down, so integrations are relevant mainly for legacy or migration scenarios. SAP Hana: System-versioned temporal tables are supported only on column store tables, not on the row store. Stacksync's field mapping accounts for these differences between Rockset 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 Rockset 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 Rockset and SAP Hana connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Rockset–SAP Hana integration in-house.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 536 integrations available for Rockset and SAP Hana.