Non-ASE servers

With Replication Server 15.2, you can use connection profiles to connect to non-ASE servers with simplified installation and configuration. To prepare non-ASE databases for replication, see the Replication Server Heterogeneous Replication Guide.


Simplified installation and configuration

You do not need to edit and execute scripts to install datatype definitions, function strings, and class-level translations for heterogeneous (non-ASE) datatype support. The functions provided by the scripts are included as part of the Replication Server installation, or are included in connection profiles that are installed with Replication Server. These enhancements simplify installation and configuration for heterogeneous and non-ASE environments. Follow the simplified configuration instructions in Chapter 8, “Installing and Implementing Heterogeneous Datatype Support” in the Replication Server Configuration Guide for your platform.

In addition, Replication Server 15.2 and later provides error class support for non-ASE replicate databases. See “Data server error handling” on page 280 in the Replication Server Administration Guide Volume 2.


Connection profiles

You can use connection profiles that contain connection configurations and replicate database object definitions relevant to each type of actively supported non-ASE data server. You can use these connection profiles and simple syntax to create connections between actively supported data servers such as Adaptive Server Enterprise, IBM DB2, Microsoft SQL Server, and Oracle. Replication Server uses the connection profile to configure the connection and create replicate database objects for you.

Connection profiles specify the function-string class, error class, and class-level translations to be installed. You can also use connection profile options to specify other actions such as whether commands should be batched and the command separator to use. See “Creating database connections” to create connections using connection profiles.

NoteWhen you create a connection using a connection profile, the system table services (STS) caches are refreshed so that you do not need to restart Replication Server.

See “Command batching for non-ASE servers” on page 47 in the Replication Server Administration Guide Volume 2.