Canonical: https://molo17.com/solutions/sap-hana-cdc/ Markdown mirror: https://molo17.com/solutions/sap-hana-cdc/index.md Title: SAP HANA CDC and real-time replication | MOLO17 Description: SAP HANA CDC with shadow audit tables polled by the agent. Replicate to warehouses, Kafka, and NoSQL in real time with Gluesync by MOLO17. Start a trial. [Solutions](/solutions/) SAP HANA CDC SOLUTION · SAP HANA CDC # SAP HANA change data capture and real-time data replication **Change capture from SAP HANA through shadow audit tables that the agent polls, instead of polling your business tables.** Gluesync by MOLO17 captures `INSERT`, `UPDATE`, and `DELETE` changes from SAP HANA with a dedicated source agent. The agent creates a shadow audit table for each captured table and polls it for new changes, then delivers those changes to the databases, warehouses, lakes, and event streams your teams already use. Manage every pipeline from the Core Hub web UI, the Gluesync control plane. [Start a Gluesync trial](/get-gluesync/) [Talk to us](/contacts/) WHO THIS IS FOR ## SAP HANA teams moving operational data into modern platforms - SAP HANA DBAs who must approve a new workload, with a documented list of grants, the audit tables the agent creates, and a retention setting they can size before anything runs - Data platform leads feeding Snowflake, Amazon Redshift, BigQuery, Kafka, or data lakes from HANA, who want one control plane for sources and targets instead of a stack of scripts and connectors - Engineers who built their own audit-table, trigger, or polling jobs against HANA and now own cleanup, restarts, and on-call for a pipeline the business treats as infrastructure - Teams replacing a generic replication tool or a one-off extract job that does not reach the target they need, and comparing a supported HANA agent with a DIY rebuild THE PROBLEM ## SAP HANA data that moves in batches goes stale Batch extracts and scheduled queries leave analytics and downstream applications working from a copy that is already behind the system of record. Teams that need HANA data in a warehouse, a lake, or a Kafka topic usually choose between full-table reloads that read production tables, custom audit or polling jobs they must maintain, or a generic replication tool that was not built around how HANA records changes. Gluesync addresses that pattern with **per-agent CDC**. The SAP HANA agent maintains shadow audit tables for the tables you select, polls them for new changes, and hands those changes to the target agents you configure, all under one Core Hub. HOW IT WORKS ## How Gluesync does SAP HANA CDC ### Shadow audit tables, polled by the agent For each table you capture, the agent creates and manages a shadow audit table, kept current by triggers, and polls it at a regular interval for new rows. - `OPERATION` (I, U, or D), `COMMIT_ID`, and `COMMIT_TIME` on every audit row, with the primary key values and data columns - Before and after images for `UPDATE` operations, enabled automatically - Row store and column store tables, plus SAP HANA user-defined types - Full-table snapshots for initial syncs or periodic reseeding ### What your DBA will be asked to grant The agent runs as a dedicated database user. The setup guide lists these privileges. Adapt them to your schemas and review them before you approve the workload. - `SELECT` on the source schema, to read the captured tables - `CREATE ANY` on the source schema, so the agent can create its shadow audit tables - `CREATE SCHEMA`, and full privileges on the schema that holds Gluesync's CDC metadata and staging ### Connectivity, TLS, and SAP HANA Cloud - Default ports are `30015` for single-tenant systems and `30013` for multi-tenant (MDC) systems. Set the tenant database name for MDC - TLS is off by default and can be enabled per connection. SAP HANA Cloud requires TLS on port `443` - Gluesync bundles the official SAP HANA JDBC driver (`ngdbc`) ### Plan shadow table retention before go-live Shadow audit tables grow with source DML until the agent processes the rows and removes them. The agent deletes processed records older than a configurable retention period. The retention purge also covers stopped entities, so set retention against the longest stop you expect. - Confirm the agent is processing changes, and monitor audit table size from the first day - For high-volume tables, adjust the CDC polling interval and query parallelism in Core Hub configuration ### Architecture around Core Hub Lightweight agents sit close to each system; Core Hub hosts the web UI and REST APIs and routes changes between source and target agents. A pipeline groups the HANA source agent, its target agents, and the entities they replicate. The SAP HANA agent works as a source and as a target, so HANA can also be the destination. Core Hub and agents deploy with Docker, Docker Compose, or Kubernetes. [Explore the general CDC streaming architecture →](/solutions/cdc-streaming/) CAPTURE OPTIONS ## The SAP HANA agent: one agent for source and target One SAP HANA agent serves the source and the target role, so the decision is whether polled shadow-table capture fits your change volume and latency needs. | Agent | Capture technique | Versions | Best for | | --- | --- | --- | --- | | [SAP HANA agent ↗](https://docs.molo17.com/gluesync/latest/agents/saphana-intro.html) | Shadow audit tables, maintained by triggers and polled by the agent. Not log-based | SAP HANA 2.0 SPS04 and later, including SAP HANA Cloud | Any SAP HANA source where polled change capture and a shadow-table retention window fit your change volume and latency needs. | TARGETS AND TOPOLOGIES ## Keep SAP HANA as the source or the destination Use the [integrations directory](/integrations/?source=SAP+HANA#integration-finder) to pair SAP HANA as source or target with relational engines, NoSQL stores, cloud warehouses, object and lake storage, or event streams, subject to each agent's documented source and target role. As a target, the agent writes over the bundled JDBC driver with TLS and bulk loads with `MERGE`. Gluesync keeps pace with your change volume at any scale. [MOLO17 Professional Services](/solutions/professional-services/) can size the deployment with your team. Target agents write in optimized batches, never row by row, and switch to native bulk load for both snapshots and CDC on targets such as [Snowflake](/solutions/replicate-to-snowflake/), [Google BigQuery](/solutions/replicate-to-bigquery/), [Amazon Redshift](/solutions/replicate-to-redshift/), [Microsoft SQL Server](/solutions/replicate-to-sql-server/), and [PostgreSQL](/solutions/replicate-to-postgresql/). - Offload reporting reads from HANA to another database: see [database offload](/solutions/database-offload/) - Keep Snowflake, Amazon Redshift, BigQuery, or a data lake in step with HANA: see [warehouse sync](/solutions/warehouse-sync/) - Publish HANA changes to Apache Kafka or another event-streaming platform - Keep HANA and a cloud target aligned with a snapshot plus CDC until cutover: see [cloud migration](/solutions/cloud-migration/) FAIR, HIGH-LEVEL COMPARISON ## Where Gluesync fits among SAP HANA CDC approaches | Approach | What buyers usually get | Where Gluesync fits | | --- | --- | --- | | SAP-provided replication tooling | Native to the SAP landscape; capabilities and supported targets depend on the tool and its release, so check each target you need | A supported HANA agent under Core Hub that delivers to targets outside the SAP stack from one control plane; see the [integrations directory](/integrations/?source=SAP+HANA#integration-finder) | | Kafka-based CDC stacks (Kafka plus Kafka Connect) | Open-source connectors; you run Kafka, Kafka Connect, offsets, sinks, and upgrades yourself | A productized HANA agent with Core Hub operations and [best-in-class MOLO17 enterprise support (rated 4.9/5 by customers)](/support/#customer-ratings); read the [Debezium alternative](/solutions/debezium-alternative/) comparison | | Qlik Replicate or Fivetran HVR-class commercial CDC | Mature replication portfolios with broad source coverage; HANA support, capture methods, and targets vary by product and version | Agent-based commercial CDC for HANA with Core Hub operations; see [migrating to Gluesync](/migrate-to-gluesync/) for supported paths | | Cloud-managed CDC services | Convenient inside one cloud provider; source support and targets follow that provider's constraints | Agents run where HANA runs, deployed with Docker, Docker Compose, or Kubernetes, and deliver to targets beyond a single provider | | DIY audit-table scripts and timestamp polling | Full control with high build and operations cost; repeated table scans and polling can compete with production work | A productized agent with snapshots, retention controls, and Core Hub monitoring; see the [SAP HANA source setup guide ↗](https://docs.molo17.com/gluesync/latest/agents/saphana-triggers.html) | RELATED CONTENT ## SAP HANA CDC research and implementation detail - [SAP HANA agent for Gluesync: real-time CDC for SAP environments](/blog/sap-hana-agent-for-gluesync-real-time-cdc-for-sap-environments/) - [Amazon RedShift target agent: high-performance cloud data warehousing with Gluesync](/blog/amazon-redshift-target-agent-high-performance-cloud-data-warehousing-with-gluesync/) - [Keep cloud warehouses synchronized with operations](/solutions/warehouse-sync/) - [CDC streaming without source overhead](/solutions/cdc-streaming/) - [SAP HANA agent overview ↗](https://docs.molo17.com/gluesync/latest/agents/saphana-intro.html) - [SAP HANA source setup ↗](https://docs.molo17.com/gluesync/latest/agents/saphana-triggers.html) - [SAP HANA target setup ↗](https://docs.molo17.com/gluesync/latest/agents/saphana-target.html) FAQ ## SAP HANA CDC questions What is SAP HANA CDC with Gluesync? Change data capture from SAP HANA through shadow audit tables. The agent creates an audit table for each captured table, records inserts, updates, and deletes with OPERATION, COMMIT\_ID, and COMMIT\_TIME, polls those tables for new changes, and delivers them to configured targets through Core Hub. Which SAP HANA versions does the agent support? SAP HANA 2.0 SPS04 and later, including SAP HANA Cloud. Is SAP HANA capture log-based? Capture uses shadow audit tables that the agent polls at a regular interval, which keeps the setup to grants on the source schema with no redo or log configuration. The polling interval is configurable, so you decide how fresh the targets stay. What does the DBA have to grant? SELECT on the source schema, CREATE ANY on the source schema so the agent can create its shadow audit tables, and CREATE SCHEMA plus full privileges on the schema that holds Gluesync's CDC metadata and staging. How long are shadow audit records kept? Retention is configurable. The agent deletes processed records older than the retention period you set. The retention purge also covers stopped entities, so size retention against the longest stop you expect. Does Gluesync work with SAP HANA Cloud? Yes, as a source and as a target. Use TLS and port 443. Can Gluesync write into SAP HANA as well as read from it? Yes. The SAP HANA target agent writes over TLS with the bundled JDBC driver, bulk loads with MERGE, and supports the TRUNCATE before snapshot option in Core Hub. CDC BY SOURCE DATABASE ## Other sources Gluesync captures from - [Cosmos DB CDC](/solutions/cosmos-db-cdc/) - [Couchbase CDC](/solutions/couchbase-cdc/) - [Db2 LUW CDC](/solutions/db2-luw-cdc/) - [DynamoDB CDC](/solutions/dynamodb-cdc/) - [IBM i CDC](/solutions/ibm-i-cdc/) - [Informix CDC](/solutions/informix-cdc/) - [MariaDB CDC](/solutions/mariadb-cdc/) - [MongoDB CDC](/solutions/mongodb-cdc/) - [MySQL CDC](/solutions/mysql-cdc/) - [Oracle CDC](/solutions/oracle-cdc/) - [PostgreSQL CDC](/solutions/postgresql-cdc/) - [SAP ASE (Sybase) CDC](/solutions/sap-ase-cdc/) - [ScyllaDB CDC](/solutions/scylladb-cdc/) - [SQL Server CDC](/solutions/sql-server-cdc/) - [YugabyteDB CDC](/solutions/yugabytedb-cdc/) ## Evaluate Gluesync with your SAP HANA tables Start a trial on your infrastructure, or talk to MOLO17 about the grants, retention settings, and targets for your HANA estate. [Start a Gluesync trial](/get-gluesync/) [Talk to MOLO17](/contacts/)