Targets
Sybase ASE
Replicate into an SAP ASE (Sybase) database, with the connection, permissions, objects and options a Sybase target uses.
A Sybase ASE target receives the initial load and the streamed changes through the agent's database connection. The wizard lists it as Sybase. SQL Flow applies changes to ASE in source order, one change at a time.
Requirements
| Requirement | Details |
|---|---|
| Sources | Every source and capture mode. |
| Connection | Host, Port (default 5000), Database, Username and a password or secret reference. All target tables live in the database named in Database. |
| Encryption | With Encryption at Require (default), the ASE server must accept SSL on the port you enter, and the agent validates its certificate and host name against the agent host's trust store or the file in Trusted certificate file on agent. Prefer connects without encryption unless a trusted certificate file is set. See Sybase ASE: Encrypted data. |
| Target owner | Tables with no mapped owner go to dbo. |
| Keys | Each target table needs a primary key or a unique index on the source key columns. |
Permissions
SQL Flow doesn't check the target login's permissions up front; a missing permission surfaces as the ASE error from the statement that needed it. The login needs:
- A user in the target database.
select,insert,updateanddeleteon each target table.create table, if SQL Flow creates the target tables, and permission to create an index on an existing table that lacks a key.- Ownership of the target tables, to apply source schema changes (added and dropped columns). See Schema changes by target.
For example, as the database owner:
use <database>
go
sp_adduser <login>
go
grant create table to <login>
go
grant select, insert, update, delete on <owner>.<table> to <login>
goReplace <database>, <login> and <owner>.<table> with your values.
SQL Flow creates a table with no mapped owner as dbo.<table>, and ASE lets only the database owner create objects owned by dbo. If the login isn't the database owner, either connect with a login aliased to dbo in the target database (sp_addalias <login>, dbo), or map the target owner to the login's own user name in Table and column names.
What SQL Flow creates on the target
| Object | When | Where |
|---|---|---|
| Target tables, with the source key as the primary key | Only after you confirm Prepare target schema in the wizard | The mapped owner, or dbo, in the connection's database |
A unique index named ux_<table>_<columns> | When an existing table has no unique index on the source key columns | On that table |
SQL Flow also keeps the pipeline's committed position on the target, so another agent can take over and resume from what the target holds. See High availability for agents.
When SQL Flow creates a table, it chooses the ASE type from the source value type:
| Source value | ASE column |
|---|---|
| Text | varchar(1024); varchar(255) in a key |
| Binary | image; varbinary(255) in a key |
| Boolean | tinyint (ASE bit can't be null) |
| 16-bit, 32-bit and 64-bit integers | smallint, int, bigint |
| Unsigned 64-bit integer | decimal(20) |
| Decimal | decimal(38, 18) |
| Double, float | float, real |
| GUID | varchar(36) |
| Date and time, with or without offset | datetime (the offset isn't kept) |
| Time span | time |
Create the target tables yourself when your data needs other types or lengths, for example text longer than 1,024 characters. See Data type mapping.
Options
These appear on the wizard's Target step after you choose Sybase. There is no Collapse row versions box, because Sybase ASE targets always apply changes in order.
| Option | Default | Effect |
|---|---|---|
| Atomic transaction limits: Maximum records per transaction | 1,000,000 (maximum 10,000,000) | Apply stops if one source transaction exceeds the limit, keeping the transaction intact for recovery. |
| Atomic transaction limits: Maximum transaction size (MiB) | 512 | The same, by size. |
Limitations
- Ordered apply only: every change is applied in source order, one at a time.
- Generated types: in tables SQL Flow creates, text is
varchar(1024)and key text isvarchar(255), decimals keep 18 digits after the point and 20 before it, and date-time offsets are dropped. - One database per connection: a mapped table name qualified with another database is refused with
Target provisioning does not support a catalog-qualified mapped table.
