1. OBJETIVOS
1.2 OBJETIVOS ESPECÍFICOS
The heterogeneous datatype support (HDS) feature of Replication Server provides configuration information that allows you to set up the HDS feature in the replicate Replication Server and the Microsoft SQL Server replicate database.
The configuration information is part of the installation and part of the connection profile: • Replication Server installation:
• Create function strings, error classes, and user defined datatypes • Connection profile:
• Apply class-level datatype translations to RSSD • Create objects in the Microsoft SQL Server database • Set connection properties
• Additional settings: • Settings in ECDA
• Settings for Dynamic SQL • Settings for Command batching
See also
• Class-Level Datatype Translations to RSSD on page 95
• Objects in the Microsoft SQL Server Database and Connection Properties on page 96
Replication Server Installation
Replication Server installation automatically installs the required function strings and classes to support replication.
Function Strings, Error Classes, and User Defined Datatypes
Function strings are added to the Replication Server default rs_msss_function_class. The function string replaces several default Replication Server function strings with custom function strings designed to communicate with Microsoft SQL Server and access the tables and procedures that were created.
To find the error action defined for an error class, see Replication Server Reference Manual > RSSD Stored Procedures > rs_helperror.
Connection Profiles
Connection profiles allow you to configure your connection with a predefined set of properties that match your primary and replicate database replication requirements.
Syntax
create connection to data_server.database using profile connection_profile;version set username [to] user
[other_create_connection_options] [display_only]
Parameters
data_server – The data server that holds the database to be added to the replication system. database – The database to be added to the replication system.
connection_profile – Indicates the connection profile that you want to use to configure a connection, modify the RSSD, and build replicate database objects.
version – Specifies the connection profile version to use.
user – The login name of the Replication Server maintenance user for the database. Replication Server uses this login name to maintain replicated data. You must specify a user name if network-based security is not enabled.
other_create_connection_options – Use the other create connection options to set connection options not specified in the profile, such as setting your password, or to override options specified in the profile, such as specifying a custom function string class to override the function string class provided in Replication Server. See the Replication Server Reference Manual > Replication Server Commands > create connection for a complete list of the other options for create connection command.
display_only – Use display_only with the using profile clause to display the commands that will be executed and the names of the servers upon which the commands will be executed. See the client and Replication Server logs for the result of using display_only.
Class-Level Datatype Translations to RSSD
Class-level translations identify primary datatypes and the replicate datatypes into which data is to be translated (for example, DB2 UDB TIMESTAMP should be translated to Microsoft SQL Server datetime).
Note: These translations can affect Replication Server performance. Only the translations needed for your specific primary database and replicate database should be applied to the RSSD.
These connection profiles supply class-level translation for the Microsoft SQL Server replicate database:
• rs_db2_to_msss – installs Adaptive Server-to-Microsoft SQL Server class-level translations.
• rs_ase_to_msss.sql – translates Adaptive Server datatypes to Microsoft SQL Server datatypes.
• rs_udb_to_msss – translates DB2 UDB (for UNIX and Windows) datatypes to Microsoft SQL Server datatypes.
• rs_oracle_to_msss – translates Oracle datatypes to Microsoft SQL Server datatypes.
To see all the available profiles, use the admin show_connection_profiles command. Objects in the Microsoft SQL Server Database and Connection Properties The connection profile creates the RS_INFO, RS_LASTCOMMIT, and
RS_TICKET_HISTORY tables in the replicate database. The connection profiles set these connection properties: set error class rs_msss_error_class
set function string rs_msss_function_class
Additional Settings
Learn about the additional settings provided to support replication. The settings include:
• Settings in ECDA
Use the following settings in the ECDA configuration file: Transaction Mode = long
allocate = connect
SQL transformation = Sybase
When set batch is “on,” you must also specify: DelimitSqlRequests = yes
If you have a tinyint datatype at the replicate table, the following parameter must be added to the Datatype Conversion section of the Microsoft SQL service in ECDA Microsoft SQL Server.
TinyIntResults=tinyint • Settings for Dynamic SQL
Dynamic SQL is supported as of Replication Server 15.0.1 and requires ECDA Option for ODBC 12.6.1 ESD #2, or later.
• Settings for command batching
Command batching allows Replication Server to send multiple commands to the data server as a single command batch. You can put multiple commands in a language function-
string output template, separating them with semicolons (;). If the database is configured to allow command batches, which is the default, Replication Server replaces the semicolons with that connection’s DSI command separator character before sending the function string in a single batch to the data server. The separator character is defined in the
dsi_cmd_separator option of the alter connection command.
If the connection to the database is not configured to allow batches, Replication Server sends the commands in the function string to the data server one at a time. To enable or disable batching for a database, use the alter connection command.
To use command batching, enter: batch = on
batch_begin = on or off
The use of on for batch_begin reduces the number of network transfers. use_batch_markers = off
Additional batch markers are not required.
When set batch is “on,” you must also specify the following configuration: dsi_cmd_seperator set = ;
If you do not specify this configuration, ECDA ignores the commits after each batch , and all the replicate requests are rolled back after the dsi connection fades out.
For information on setting batch and dsi_cmd_separator options, see the Replication Server Reference Manual > alter connection.