Two-way sync
Changes in SAP Hana or TiDB instantly reflect in both systems. No stale data, no manual imports.
Keep SAP Hana and TiDB in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
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 TiDB 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.
Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.
Keep the same dataset live in both SAP Hana and TiDB, so each workload runs on the engine that suits it.
When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.
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 | TiDB objects | How this pairing syncs | |
|---|---|---|---|
| Sequences Server-generated key values; relevant when writing rows into tables whose identity is assigned HANA-side rather than by the source system. | Sequences Server-side ID generation relevant when external systems write rows. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| SQL views Standard database views; read-only projections synced outbound when the source data should not be exposed as raw base tables. | Indexes Secondary indexes that keep incremental sync queries efficient. | SQL views is specific to SAP Hana and Indexes to TiDB — each maps to any object or custom field on the other side. | |
| Schemas Namespaces that group tables and views; the connector targets a schema and enumerates its objects from the catalog to build the sync. | Databases MySQL-style schemas addressed by any MySQL-compatible client. | Schemas is specific to SAP Hana and Databases to TiDB — each maps to any object or custom field on the other side. | |
| 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. | Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC. | Triggers is specific to SAP Hana and Tables to TiDB — 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. | Views Logical views for shaping reads before syncing outward. | System-versioned temporal tables is specific to SAP Hana and Views to TiDB — 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. | Columns MySQL-compatible types mapped to fields in the paired system. | System views (SYS schema) is specific to SAP Hana and Columns to TiDB — 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.
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 TiDB as a row-level write, with types converted between the two schemas.
DetectionChanges in TiDB are captured at the source via change data capture — no polling loop against its API. Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks.
DeliveryEach detected change is applied to SAP Hana as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every SAP Hana–TiDB connection.
Changes in SAP Hana or TiDB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever SAP Hana or TiDB data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single SAP Hana or TiDB record.
Track your SAP Hana ⇄ TiDB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between SAP Hana and TiDB.
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 SAP Hana and TiDB 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 SAP Hana and TiDB 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 SAP Hana and TiDB: authenticate both systems, choose the objects to sync (such as SAP Hana's Sequences and SQL views), map fields visually, and changes propagate both ways in milliseconds — no code required.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed SAP Hana and TiDB connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom SAP Hana–TiDB integration in-house.
Yes — Stacksync ships production-grade connectors for both SAP Hana and TiDB. 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 TiDB: Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks; polling also works. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the SAP Hana side: Column store tables, Row store tables, Calculation views, SQL views, plus custom fields where SAP Hana exposes them. On the TiDB side: Columns, Indexes, Sequences, Databases. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
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 463 integrations available for SAP Hana and TiDB.