Set up a SAP ASE log reader source without triggers

Create the login and give it the role:

sp_addlogin gluesync_admin, <a strong password>
go
grant role sa_role to gluesync_admin
go

Add the login as a user of the source database:

use demo
go
sp_adduser gluesync_admin, gluesync_admin
go

Check the version and the state of the RepAgent threads:

select @@version
go
sp_configure 'enable rep agent threads'
go

Choose the LTL listen port. The default is 5500. Open it in the firewall between the ASE host and Core Hub, in that direction;

Choose the name that ASE uses to reach Core Hub. It becomes the LTL advertised host and it is written into ASE. It must resolve from the ASE host, and it must be a bare host name or address: no port, no spaces;

If Core Hub runs in Docker, publish the port and use the address of the Docker host as the advertised host:

services:
  gluesync-core-hub:
    ports:
      - "5500:5500"

From the ASE host, check that the name resolves and the port answers. Replace <core hub host>:

getent hosts <core hub host>
nc -zv <core hub host> 5500

In the Control Plane, select Create your first pipeline, or the + button of the pipeline list if you already have pipelines. The Agents setup wizard opens;

In 1. Setup source, search for sybase and select the SAP (Sybase) ASE tile. It offers two connectors. Select SAP (Sybase) ASE Log Reader agent, not the Triggers agent;

In Base settings, fill in the connection:

Fill in the log reader fields in the same tab:

Select Test and continue. The source appears with a green check mark. Select Next.

In 2. Setup target(s), search for postgres, choose the PostgreSQL CDC agent tile and fill Base settings: Host name / Address, Port (5432), Database name, Username and Password. Select Test and continue. The target appears with a green check mark. Select Next;

In 3. Ready, enter a Pipeline name, for example ASE to PostgreSQL, and select Finish.

In the pipeline, select Entities. The Add entities page opens with the Object browser. Expand the schema dbo and select the table orders. The Field mapping dialog opens;

Under Target, open Target Schema and select public. In Target Table type orders and choose Create table "orders". The dialog shows New table orders will be created on confirm. and proposes the target types;

Two fields show a red error and Missing required field appears at the top: the Precision of the datetime column (created) and the Length of the text column (notes). Enter 6 as the precision of created. Enter a length for notes, for example 1000000. PostgreSQL stores the column as plain text whatever the length is. The Confirm button turns blue;

Select Confirm. The Create table orders dialog shows the read-only SQL statement. Read it, then select Create table orders to run it on PostgreSQL;

Back on the Add entities page, select Confirm and continue.

In the pipeline, select the play button of the entity. The Sync changes (CDC) dialog opens;

Under Start from keep Full copy, recommended for the first start: it copies all rows, then follows the changes. Under Data already in the target keep Keep and merge;

Select Start entity.

Look at the log space and at the truncation point:

use demo
go
sp_spaceused syslogs
go
dbcc gettrunc
go

Decide how long an outage you accept. Multiply the log volume per hour at peak by that time, and size the log device for it;

Set an alert on the log space, so that you act before ASE refuses writes. Gluesync also posts a warning when a stopped stream keeps more of the log than Warn when a stopped stream keeps more of the log than (MB) allows (1024 by default, 0 switches it off).

Create a login that has no role and can only read the table, and use it as the Username of the source:

sp_addlogin gluesync_ro, <password>
go
use demo
go
sp_adduser gluesync_ro, gluesync_ro
go
grant select on dbo.orders to gluesync_ro
go

Create a second pipeline on the same database with another LTL listen port, such as 5501, and add an entity. The page shows The Replication Agent of database 'demo' already sends to 'gluesync-core-hub:5500', not to this agent ('gluesync-core-hub:5501'). Another Replication Server may depend on it: set 'forceRepAgentTakeover' to point it at this agent instead. Gluesync refuses to change the RepAgent. Fix: use the triggers agent for this database, or remove the other replication and set Force Replication Agent takeover to true;

Change the LTL advertised host of a pipeline that runs to a name that does not exist, and select Test and continue. The Core Hub log shows Pointing the Replication Agent of database demo from gluesync-core-hub:5500 to corehub-wrong:5500 as a warning: ASE now sends to the wrong host. The ASE error log shows RepAgent(4): The Rep Agent Thread will retry the connection to the Replication Server every 10 second(s). (RepSvr = corehub-wrong:5500). and, for a name that does not resolve, Protocol driver call to parse connection information failed. The RepAgent cannot connect, so no change is delivered while the name is wrong. Fix: enter the right name and select Test and continue again. The log shows Pointing the Replication Agent of database demo from corehub-wrong:5500 to gluesync-core-hub:5500, the next Replication Agent of …​ connected line follows, and a row that you insert afterwards reaches the target.