You must consider the following issues in a non-Sybase primary to Adaptive Server replicate configuration:
The Replication Server database connection for the primary database must include a valid user ID and password for the primary database, even though this user ID does not apply transactions to the primary database in this configuration.
If you use a Replication Server heterogeneous datatype support (HDS) datatype definition to define a column’s datatype in a replication definition, the hds_clt_xxx_to_ase.sql script must be applied to the RSSD of the replicate Replication Server to provide automatic translation of that primary database datatype to an Adaptive Server native datatype.
If you can use Replication Server native datatypes to represent all the primary column datatypes (that is, no datatype definitions are required), then no HDS translation scripts need be applied.
Sybase recommends that you do not configure the Replication Agent to perform any datatype translation, unless all replicate databases require the data in that translated form. In that case, it may be a more effective use of resources to let the Replication Agent do the translation once, rather than having replicate Replication Servers do it for each replicate database.
