Real-time data replication to SAP HANA from SAP and non-SAP systems

• SAP data architects who model on HANA and need tables kept current from SAP and non-SAP sources, created in the column store by default and merged by key as changes arrive
• Data platform leads feeding SAP HANA from Oracle, SQL Server, SAP ASE, PostgreSQL, or MongoDB who want one Core Hub for every source, backed by best-in-class enterprise support, rated 4.9/5 by customers
• BASIS teams and architects running single-tenant, multi-tenant, and HANA Cloud landscapes, who need the right port per deployment, TLS, and a short, explicit privilege set for the target user
• Engineers replacing scheduled extracts, hand-written MERGE scripts, or a JDBC sink chain who want every source delivered to HANA by one product, with snapshots and monitoring built in

The write path: MERGE upserts over the SAP HANA JDBC driver

The SAP HANA agent connects through the official SAP HANA JDBC driver (ngdbc), bundled with Gluesync, with TLS switched on per connection. It is a target agent: it receives changes from any Gluesync source agent and writes them straight into your tables, with no intermediate file buffers. Inserts and updates are applied with HANA's own MERGE statement, so a row that already exists is updated in place and a new key is inserted, and every batch lands as current rows.

• One agent, both directions: the same agent also captures changes from HANA through shadow tables, so a HANA system can be the target of one pipeline and the source of another. See SAP HANA CDC.

Optimized batches, never row by row

Gluesync never writes one row at a time to SAP HANA. Incoming changes are grouped into chunks and each chunk is applied as one batched MERGE, which cuts network round-trips and keeps the load on the HANA system predictable. The chunk size is configurable on the target agent, so you can push more rows per statement during an initial load or keep transactions short while HANA serves analytical queries.

Snapshot first, then continuous CDC

• Seed, then stream: full-table snapshots load each table into HANA, for the initial sync or a later reseed, then the entity switches to CDC from its source agent.
• TRUNCATE before snapshot: when the Core Hub option is enabled, the HANA table is truncated before a snapshot reload, for a clean start.
• Parallel loads: snapshot writing concurrency is configurable per entity, and logical partitioning splits large source tables into ranges read in parallel.
• Resume: an interrupted snapshot resumes from its last saved state when you start the entity again.
• Scheduled refreshes: the Chronos Scheduler runs snapshots on a cadence for tables you prefer to reload. See schedules and events.

Tables, storage, and duplicate keys

• Column store by default: tables that Gluesync creates in HANA use the column store, the format HANA is built for in analytical workloads. Row store tables are supported as well.
• On duplicate key: Upsert, the default, overwrites the target row with the incoming one. Skip keeps the row on HANA and raises a warning in Notifications Hub that lists the skipped keys. Fail stops the entity and leaves the source unchanged, so restarting the entity replays the same transaction.
• Shaping on the way in: Custom Field Functions and Allowed Operations per entity let you rename or compose columns, or keep history tables by not forwarding DELETE. See data transformation.

What your SAP HANA administrator sets up

Create a user for Gluesync and grant it what the writes need. For the full walkthrough, see the SAP HANA target setup guide ↗.

1. Create the user with NO FORCE_FIRST_PASSWORD_CHANGE, so the agent signs in without a password reset.
2. Allow table creation: grant the user CREATE ANY on the target schema.
3. Allow the writes: grant the user SELECT, INSERT, UPDATE, and DELETE on the target schema.
4. In Core Hub, enter the host and the port: 30015 for a single-tenant system, 30013 for a multi-tenant database container (with the tenant database name), or 443 for SAP HANA Cloud.
5. Switch on TLS for SAP HANA Cloud, which requires it, and for on-premises systems whose server has SSL certificates configured.

Architecture around Core Hub

Lightweight agents sit close to each source and to HANA. Core Hub orchestrates them through its web UI and REST APIs and routes changes to the SAP HANA agent. A pipeline groups a source agent, the SAP HANA agent, and the entities they replicate, and several pipelines can merge into the same HANA schema. Core Hub and agents deploy with Docker, Docker Compose, or Kubernetes, on-premises or in any cloud. See CDC streaming.

Explore the general CDC streaming architecture →

Any Gluesync source agent can feed SAP HANA, each with its own native capture technique. Open the integrations finder with SAP HANA pre-selected to see every source you can pair with it.

One Core Hub runs several sources into the same HANA system side by side, with the same snapshot, monitoring, and duplicate-key policy for each entity. Gluesync keeps pace with your change volume at any scale, and batch sizes are configurable per agent. MOLO17 Professional Services can plan the landscape and the privileges with your BASIS team.

• SAP ASE to SAP HANA, for landscapes moving data off an ASE estate or running both side by side: see SAP ASE CDC
• Oracle to SAP HANA from the redo logs through LogMiner or XStream: see Oracle CDC
• SQL Server to SAP HANA through Change Data Capture or Change Tracking, keeping a HANA reporting layer current: see SQL Server CDC
• IBM i (AS/400) to SAP HANA through the native journal APIs: see IBM i CDC