SOLUTION · SAP ASE (SYBASE) CDC

SAP ASE (Sybase) change data capture and real-time data replication

Trigger-based CDC for SAP ASE 15.7 and later, with the trigger setup and privileges spelled out before you approve it.

Gluesync by MOLO17 captures committed INSERT, UPDATE, and DELETE events from SAP Adaptive Server Enterprise (SAP ASE, also known as Sybase ASE) with a dedicated source agent. The agent installs and manages its triggers on the tables you select, connects through a built-in JDBC driver, and delivers the changes continuously 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 Talk to us

WHO THIS IS FOR

SAP ASE teams moving core transactional data into modern platforms

DBAs who must approve triggers on production SAP ASE tables. They need the exact privileges and the one-trigger-per-operation rule in writing before they sign off
Data platform leads feeding warehouses, data lakes, Kafka, or Couchbase from SAP ASE systems of record, who want one Core Hub for sources and targets instead of a stack of connectors
Teams reviewing SAP-native replication or commercial CDC renewals for ASE who want heterogeneous targets and best-in-class enterprise support from MOLO17, rated 4.9/5 by customers
Engineers who built batch extracts or timestamp polling for ASE and now own the schedules, retries, and on-call rotation for a pipeline the business treats as infrastructure

THE PROBLEM

SAP ASE data that only moves in batches becomes stale

SAP ASE usually runs core transactional systems, so scheduled extracts and polling jobs leave warehouses and applications working from copies that are already behind, while competing with production for resources. Buyers searching for Sybase CDC or SAP ASE replication usually weigh SAP's own replication stack, commercial CDC products, and Kafka-based pipelines, and each one brings its own licensing, operations, or source-support question.

Gluesync addresses that pattern with per-agent CDC: the SAP ASE agent captures committed changes with triggers, and target agents write to the destination you choose, all under one Core Hub.

HOW IT WORKS

How Gluesync does SAP ASE (Sybase) CDC

Triggers on each audited table, managed by Gluesync

The SAP (Sybase) ASE agent uses a triggers-based auditing structure. Gluesync installs the triggers on the tables you select, creates a CDC table for each audited table, and streams the committed events from that audit layer.

Three triggers per audited table: one each for insert, update, and delete, created automatically by the agent.
One CDC table per audited table: each trigger writes a timestamp, an operation code (I, U, or D), and the row values to a Gluesync-managed TABLENAME_CDC table.
Updates carry the new row image written by the update trigger, so the target receives the current values of the row.
Automatic trigger creation can be turned off. SAP ASE allows one trigger per operation per table. If a table already has triggers, disable automatic creation during entity setup and merge the Gluesync trigger code into your existing trigger by hand. Triggers setup docs ↗

What your DBA will be asked to enable

The agent connects with a built-in JDBC driver as a dedicated user. That user needs two things: read and write access to the audited tables, and the ability to create triggers on them.

Connection fields: host, port (default 5000), database name, username, and password, with optional TLS and a certificatePath.
Privileges: create a dedicated login for Gluesync and grant it sa_role.

Snapshots, retention, and cleanup

Snapshot jobs seed the ASE tables before CDC resumes, and snapshot concurrency is configurable.

Source change retention is configurable and sets how long change records are kept in your database.
Trim text values strips the trailing spaces that CHAR columns carry, when you want them removed before delivery.
Stopped entities are covered. The retention purge also runs for entities that are stopped, so a paused entity does not leave change records behind.

Architecture around Core Hub

Lightweight agents sit next to each system; Core Hub is the control plane for the web UI and the REST APIs, and it routes changes between source and target agents. Pipelines group the ASE source agent, its target agents, and the entities you replicate. The ASE agent documents setup through the Core Hub REST API as well as the web UI. Core Hub and agents deploy with Docker, Docker Compose, or Kubernetes.

Explore the general CDC streaming architecture →

CAPTURE OPTIONS

One SAP ASE source agent: trigger-based capture

Gluesync documents one source agent for SAP ASE, so the decision is whether trigger-based capture fits your tables, not which agent to pick.

Agent	Capture technique	Versions	Best for
SAP (Sybase) ASE agent ↗	Triggers on each audited table write committed insert, update, and delete events to a Gluesync-managed CDC table	SAP ASE 15.7 and later	SAP ASE estates where Gluesync may create triggers on the tables you audit, and where update events that carry the new row image are enough. Check whether the audited tables already have triggers, since SAP ASE allows one per operation, and merge by hand where they do.

TARGETS AND TOPOLOGIES

Keep SAP ASE as the system of record while modernizing destinations

Use the integrations directory to pair SAP (Sybase) ASE 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 through the bundled JDBC driver with TLS, and it honors the Core Hub TRUNCATE before snapshot option when that is enabled.

Gluesync keeps pace with your change volume at any scale. MOLO17 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, Google BigQuery, Amazon Redshift, Microsoft SQL Server, and PostgreSQL.

Offload reporting and API reads from SAP ASE to PostgreSQL or another database: see database offload
Feed a warehouse or data lake continuously from SAP ASE: see warehouse sync
Publish SAP ASE changes to Apache Kafka or another event-streaming platform for downstream services
Run a snapshot plus CDC to keep SAP ASE and a new target aligned until cutover: see cloud migration

FAIR, HIGH-LEVEL COMPARISON

Where Gluesync fits among SAP ASE CDC approaches

Approach	What buyers usually get	Where Gluesync fits
SAP-native replication (SAP Replication Server)	SAP's own replication for ASE estates, often the first option a Sybase shop checks; licensing and scope depend on the SAP contract	Agent-based ASE capture under one Core Hub, with targets beyond SAP systems and a documented trigger model; see the CDC streaming architecture
Debezium plus Kafka	Open-source Kafka Connect stack that you run yourselves; Debezium does not list an SAP ASE connector, so this path usually means a custom or third-party source	Productized ASE agent with Core Hub operations and MOLO17 enterprise support; no Kafka mesh required. Read the Debezium alternative comparison
Qlik Replicate, Fivetran HVR, or Syniti-class commercial CDC	Mature commercial replication with broad source coverage; ASE support, capture mode, and packaging differ by product and version, so confirm them in writing	Agent-based ASE capture under Core Hub with heterogeneous targets; Syniti Replicate estates can start from the Syniti to Gluesync hub
Cloud-managed CDC services	Convenient inside one cloud; source and target coverage follows that provider's rules, so check SAP ASE support and capture method for your version	Targets beyond a single provider under one Core Hub. The ASE capture method is triggers, so check trigger rights before you choose this path
DIY batch extracts or timestamp polling	Full control with high build and operations cost; polling and extract jobs compete with production for resources	Productized trigger-based capture with snapshots, retention cleanup, and Core Hub monitoring; setup is described in the triggers setup docs ↗

SAP ASE CDC research and implementation detail

What is SAP ASE CDC with Gluesync?

Change data capture from SAP Adaptive Server Enterprise with triggers that Gluesync installs on the tables you select. The triggers record insert, update, and delete events in a CDC table per audited table, and Gluesync delivers the committed changes to configured targets through its agents and Core Hub.

Is Sybase ASE the same product as SAP ASE?

Yes. Sybase ASE is also known as SAP Adaptive Server Enterprise, and the Gluesync agent is named SAP (Sybase) ASE.

Which SAP ASE versions does Gluesync support?

The SAP (Sybase) ASE agent is documented from SAP ASE 15.7 onward.

How does Gluesync capture changes from SAP ASE?

With triggers, which is the only capture method documented for this agent. Three triggers per audited table, one each for insert, update, and delete, write to a Gluesync-managed CDC table, and the agent streams the committed events from it.

What must the DBA enable on SAP ASE?

The Gluesync user needs read and write access to the audited tables and permission to create triggers on them. Create a dedicated login for Gluesync and grant it sa_role. SAP ASE allows one trigger per operation per table, so an existing trigger must be merged with the Gluesync trigger by hand.

Can Gluesync write to SAP ASE, not only read from it?

Yes. The agent supports the target role through a built-in JDBC driver with TLS, and it honors the TRUNCATE before snapshot option when enabled.

CDC BY SOURCE DATABASE

Other sources Gluesync captures from

Evaluate Gluesync with your SAP ASE tables

Start a trial on your infrastructure, or talk to MOLO17 about privileges, trigger setup, and targets for your SAP ASE estate.

Start a Gluesync trial Talk to MOLO17