Search docs.molo17.com

    Sybase ASE Agent for Gluesync: Features Overview

    SAP Sybase ASE logo

    Core principles

    This agent establishes a connection to SAP (Sybase) ASE via a built-in JDBC driver.

    Change data capture

    Gluesync offers two source agents for SAP (Sybase) ASE. Both read the same tables, deliver the same events, and can be used with the same target; they differ in how changes are captured:

    • Sybase ASE (log reader) (sybase-logreader), new in 2.3.1, reads the ASE transaction log through ASE’s own Replication Agent (RepAgent) thread. It creates no triggers and no shadow tables and installs nothing on the ASE host. It captures before images and truncates, and it needs ASE to connect to Core Hub on a TCP port. ASE keeps its log until Gluesync confirms the changes, and a database can have only one RepAgent. See Source data from SAP (Sybase) ASE (log reader).

    • Sybase ASE (sybase) implements a triggers-based auditing structure, which is auto-installing and fully managed by Gluesync. It needs only a connection from Gluesync to ASE, and it fits databases that cannot give a RepAgent to Gluesync. To read more about this trigger auditing structure we invite you to check out our full deep-dive on it by reading the Source data from SAP (Sybase) ASE chapter.

    Choose the log reader when you cannot or do not want to add triggers and tables to the source database, when your tables already have triggers, or when you need before images or truncate events. Choose triggers when ASE cannot reach Core Hub, or when the database is already replicated by SAP Replication Server. See Log reader or triggers.

    Supported versions

    Gluesync works on SAP (Sybase) ASE starting from version 15.7.

    Platform supported features

    Feature Support Notes

    Target role

    ✅

    Writes to SAP (Sybase) ASE via the bundled JDBC driver with TLS and pooling.

    Source role

    ✅

    Captures changes via the log reader (ASE transaction log, through RepAgent) or via the trigger-based auditing layer auto-managed by Gluesync, depending on the agent you choose.

    Snapshots

    ✅

    Snapshot jobs seed ASE tables before CDC resumes.

    CDC

    ✅

    The log reader and trigger auditing stream committed INSERT/UPDATE/DELETE events.

    CDC type

    Transaction log (log reader) or database triggers + CDC table (triggers)

    The log reader receives the decoded log from ASE’s RepAgent thread. The triggers agent writes row identifiers and CRUD metadata into the Gluesync-managed tables.

    User defined data types

    ✅

    Supports user defined data types.

    Bulk load

    ❌

    Not supported.

    Database pooling

    ✅

    Supports connection pooling for efficient resource utilization across multiple pipelines.

    Source persisted internal cache

    Log reader: ✅ / Triggers: ❌

    The log reader keeps the changes of a transaction in the agent’s cache until the transaction commits. The triggers agent does not implement caching.

    Target persisted internal cache

    ❌

    Writes go directly to ASE; no additional cache is needed.

    Driver / connector

    Built-in JDBC driver

    Vendor driver bundled with Gluesync for ASE connectivity.

    Chains

    N/A

    Not supported.

    Truncate operation support (reading)

    Log reader: ✅ / Triggers: ❌

    The log reader captures truncate table on replicated tables. Trigger logic does not detect TRUNCATE-like operations.

    Truncate operation support (writing)

    ✅

    Honors the Core Hub “TRUNCATE before snapshot” option when enabled.

    Q&A

    I have got Sybase ASE, is it supported? We do support and tested Sybase ASE (Advanced Server Enterprise) starting from version 15.7, we expect the older version to work too but are currently not yet tested.

    I have got Sybase / SAP SQL Anywhere, is it supported? SAP SQL Anywhere has its own agent, which reads the transaction log of the database. See SAP SQL Anywhere.