Real-time data replication to SAP ASE from the systems around it

• DBAs and application owners who run SAP ASE as a system of record and need its tables fed from newer platforms, with the duplicate-key behavior chosen per entity: Upsert, Skip, or Fail
• Data platform leads feeding SAP ASE from Oracle, SQL Server, PostgreSQL, SAP HANA, or Couchbase who want one Core Hub for every source instead of one connector per source, backed by best-in-class enterprise support, rated 4.9/5 by customers
• Architects planning a gradual move around an ASE estate, who need ASE and the new platform kept in step during cutover instead of a big-bang switch
• Engineers replacing a JDBC sink chain or nightly sync scripts who want every source delivered to SAP ASE by one product, with snapshots, checkpoints, and monitoring built in

The write path: a bundled JDBC driver with TLS

The SAP ASE agent connects through the vendor JDBC driver bundled with Gluesync, over TLS when you enable it. It is a target agent: it receives changes from any Gluesync source agent and writes them straight into your ASE tables, with no intermediate files or target-side store in between.

• Encryption: TLS is switched on per connection, with a certificate path when your server presents its own certificate.
• One agent, both directions: the same agent also captures changes from ASE, so an ASE server can be the target of one pipeline and the source of another. See SAP ASE CDC.

Optimized batches, never row by row

Gluesync never writes one row at a time to SAP ASE. Incoming changes are grouped into chunks and applied as SQL batch operations, which cuts network round-trips and keeps the load on the ASE server predictable, an important property on a database that is still serving its own applications. The chunk size is configurable on the target agent, so you can favor throughput during a migration window or shorter transactions while ASE carries production traffic.

Snapshot first, then continuous CDC

• Seed, then stream: snapshot jobs load each table into ASE, then the entity switches to continuous CDC from its source agent's change mechanism.
• INSERT or UPSERT: INSERT with TRUNCATE before snapshot, which the ASE agent honors, is the fast path for empty or reset tables; UPSERT merges the snapshot with rows already in ASE.
• 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 example off-hours. See schedules and events.

Duplicate keys: upsert, skip, or fail, per entity

When an insert arrives for a key that already exists in SAP ASE, you choose what happens for that entity. Upsert is the default and overwrites the target row with the incoming one. Skip keeps the row on the target, writes the rest of the transaction, 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 once the conflict is resolved.

What your SAP ASE DBA sets up

The agent needs one database user and a handful of connection details. For the full walkthrough, see the SAP ASE target setup guide ↗.

1. Create a login and database user with read and write access to the target database and its tables.
2. In Core Hub, enter the host or IP address, the port (5000 by default), the database name, and the user's credentials.
3. Switch on TLS, and give the certificate path when your ASE server uses its own certificate.

Architecture around Core Hub

Lightweight agents sit close to each system. Core Hub orchestrates them through its web UI and REST APIs and routes changes to the SAP ASE agent. A pipeline groups a source agent, the SAP ASE agent, and the entities they replicate, and several pipelines can write into the same ASE server. 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 Adaptive Server Enterprise, each with its own native capture technique. Open the integrations finder with SAP ASE pre-selected to see every source you can pair with it.

One Core Hub runs several sources into the same ASE server 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 topology and the cutover with your team.

• SAP HANA to SAP ASE, for SAP estates that keep both platforms in step: see SAP HANA CDC
• Couchbase to SAP ASE, when documents in Couchbase and rows in ASE must stay aligned, in either direction: see Couchbase CDC
• Oracle to SAP ASE from the redo logs through LogMiner or XStream: see Oracle CDC
• SQL Server to SAP ASE through Change Data Capture or Change Tracking, feeding an ASE application or reporting database: see SQL Server CDC