See all results

    SOLUTION · SAP ASE (SYBASE) CDC

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

    Log-based CDC straight from the ASE transaction log, or trigger-based CDC when only Gluesync should open connections, for SAP ASE 15.7 and later.

    Gluesync by MOLO17 captures committed INSERT, UPDATE, and DELETE events from SAP Adaptive Server Enterprise (SAP ASE, also known as Sybase ASE) with two dedicated source agents. The log reader streams changes from the transaction log through ASE's own Replication Agent thread, with no triggers, no shadow tables, and nothing installed on the ASE host. The triggers agent records changes with triggers that Gluesync installs and manages. Both deliver the changes continuously to the databases, warehouses, lakes, and event streams your teams already use, and you 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 want the source schema left untouched: the log reader adds no triggers and no tables, and the setup is either automatic with sa_role, split between roles, or a list of statements the DBA runs
    • DBAs who must approve triggers on production SAP ASE tables and 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 log reader captures committed changes from the transaction log, the triggers agent captures them with managed triggers, and target agents write to the destination you choose, all under one Core Hub. Both source agents read the same tables, deliver the same events, and use the same pipelines and snapshots.

    HOW IT WORKS

    How Gluesync does SAP ASE (Sybase) CDC

    Log reader: the ASE transaction log, through ASE's own RepAgent

    ASE ships a log reader inside the server. Its Replication Agent (RepAgent) thread scans the transaction log of one database, decodes the records of the tables marked for replication, and pushes them over TCP in the Log Transfer Language (LTL). Core Hub is that endpoint, so ASE streams every committed transaction of the replicated tables to Gluesync directly from its own log.

    • Nothing in your database: no triggers and no shadow tables, and nothing installed on the ASE host. The setup marks the tables for replication and configures the RepAgent of the database.
    • Before images: updates and deletes arrive with the before image of the row.
    • Truncates: TRUNCATE TABLE on a replicated table is captured and delivered.
    • Only committed transactions: Gluesync holds the changes of each transaction until it commits and hands only committed transactions to the pipeline.
    • Safe resume: Gluesync confirms how far it has stored the changes, ASE releases its log up to that point, and the stream resumes from there after a restart or a network failure. Log reader setup guide ↗

    No gap between snapshot and CDC

    When an entity is first set up, the tables are marked and the RepAgent is started before the snapshot begins, and the stream position is recorded. Every change made between the snapshot and the start of CDC arrives, and a row seen by both is applied once, as an upsert.

    What your DBA sets up for the log reader

    Each item is a fact your DBA can check before approving the agent.

    • One RepAgent per database: a database runs a single RepAgent, so each log reader agent reads the database named in its connection.
    1. Use SAP ASE 15.7 or later. The log reader is validated on ASE 16.0 SP02 PL02, on the Developer or Enterprise edition, and the RepAgent thread needs no licensed option beyond ASE_CORE.
    2. Create a login that can read the tables to replicate, used for the snapshot and for the table metadata.
    3. Choose how the setup runs. With sa_role, Gluesync configures ASE automatically. With split duties, sa_role is needed once for sp_configure 'enable rep agent threads', and the rest runs with replication_role and ownership of the tables. If your DBA prefers to run the statements, turn off automatic setup and Gluesync writes them to the Core Hub log.
    4. Allow ASE to connect to Core Hub on the log reader port, 5500 by default, and publish that port from the Core Hub container. Gluesync still connects to ASE on its usual port, 5000 by default.
    5. Size the ASE log retention for the longest pause you want the pipeline to ride through. ASE keeps its log until Gluesync confirms the changes.

    Triggers agent: managed triggers on each audited table

    The SAP (Sybase) ASE Triggers 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. It needs only a connection from Gluesync to ASE.

    • 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 guide ↗

    What your DBA will be asked to enable for the triggers agent

    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.
    • 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 with either agent, and snapshot concurrency is configurable.

    • Source change retention for the triggers agent 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 agents document 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

    Two SAP ASE source agents: which one to pick

    Both agents read the same tables, deliver the same events, and feed the same targets under Core Hub. They differ in how they capture changes, and that decides what your DBA sets up and which network connections you open.

    AgentCapture techniqueVersionsBest for
    SAP (Sybase) ASE Log Reader agent ↗ ASE transaction log read through ASE's own RepAgent thread, which pushes the decoded log to Core Hub over TCP in LTL; before images, truncates, and committed transactions only SAP ASE 15.7 and later; validated on ASE 16.0 SP02 PL02 Source schemas you want to leave untouched, tables that already have triggers, pipelines that need before images or truncates, and high write load. ASE connects out to Core Hub on the log reader port, 5500 by default.
    SAP (Sybase) ASE Triggers 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 Environments where only Gluesync should open connections, so ASE does not connect out, and databases that already feed SAP Replication Server. Gluesync may create triggers on the tables you audit; where a table already has triggers, merge by hand, since SAP ASE allows one per operation.

    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, Databricks, 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

    ApproachWhat buyers usually getWhere 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 The log reader uses the same RepAgent thread, with Core Hub as the endpoint, so ASE streams its log to targets beyond SAP systems under one Core Hub. Databases that already feed SAP Replication Server can use the triggers agent. 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 Two productized ASE agents 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, from the log or with triggers, 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, with a log-based and a trigger-based ASE agent, so you pick the capture method that fits your network and your DBA's rules
    DIY batch extracts or timestamp polling Full control with high build and operations cost; polling and extract jobs compete with production for resources Productized capture with snapshots, safe resume, retention cleanup, and Core Hub monitoring; setup is described in the log reader setup guide ↗ and the triggers setup guide ↗

    RELATED CONTENT

    SAP ASE CDC research and implementation detail

    FAQ

    SAP ASE (Sybase) CDC questions

    What is SAP ASE CDC with Gluesync?

    Change data capture from SAP Adaptive Server Enterprise through two source agents. The log reader reads the ASE transaction log through ASE's own RepAgent thread, and the triggers agent records changes with triggers that Gluesync installs on the tables you select. 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 agents are named SAP (Sybase) ASE.

    Which SAP ASE versions does Gluesync support?

    Both SAP (Sybase) ASE source agents work from SAP ASE 15.7 onward. The log reader is validated on ASE 16.0 SP02 PL02.

    How does Gluesync capture changes from SAP ASE?

    With the log reader, ASE's RepAgent thread scans the transaction log and pushes the decoded records to Core Hub over TCP. Gluesync holds each transaction until it commits, delivers only committed transactions, and confirms how far it has stored them so ASE can release the log and resume from there. With the triggers 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.

    Should we use the log reader or the triggers agent?

    Choose the log reader when you want the source schema untouched, when tables already have triggers, when you need before images or truncates, or when the write load is high. Choose the triggers agent when only Gluesync should open connections, so ASE does not connect out to Core Hub, or when the database already feeds SAP Replication Server. Both deliver the same events to the same targets.

    What must the DBA enable on SAP ASE?

    For the log reader, a login that reads the tables and sa_role for the automatic setup, or replication_role plus table ownership with sa_role used once to enable RepAgent threads, or the DBA runs the statements Gluesync writes to the Core Hub log. ASE then connects to Core Hub on the log reader port, 5500 by default, and the ASE log retention is sized for the longest pause you want to ride through. For the triggers agent, the Gluesync user needs read and write access to the audited tables and permission to create triggers on them, with sa_role granted to a dedicated login.

    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 the right SAP ASE agent for your network, privileges, and targets.

    Start a Gluesync trial Talk to MOLO17

    ARTICLES

    Articles about SAP ASE (Sybase)

    All articles about SAP ASE (Sybase) →