The only significant intrusions or impacts to the SQL Anywhere replicate database are the database objects created through the connection profile that creates three tables in the replicate database to support Replication Server operations:
RS_INFO contains information about the sort order and character set used by the replicate database. When using Replication Server version 12.0 or later, the replicate database sort order and character set is to be recorded in the RS_INFO table.
Confirm that the INSERT statements
for this table specify the proper character set and sort order for
your data server.
When using Replication Server version 12.0 or later, the replicate database sort order and character set must be recorded in the RS_INFO table.
The Replication Server rs_get_charset and rs_get_sortorder functions retrieve the character set and sort order from the RS_INFO table in the replicate database.
RS_LASTCOMMIT holds information about the last successfully committed replicate transaction applied to the replicate database.
Each row in the RS_LASTCOMMIT table identifies the most recent committed transaction that was distributed to the replicate database from a primary database. Replication Server uses this information to ensure that all transactions are distributed.
The Replication Server rs_get_lastcommit function retrieves information about the last transaction committed in the replicate database. For non-ASE replicate databases, the rs_get_lastcommit function is replaced in the database-specific function-string class by the query required to access the RS_LASTCOMMIT table in the replicate database.
RS_TICKET_HISTORY contains the execution results of Replication Server command rs_ticket.Issue rs_ticket for the primary database to measure the amount of time it takes for a command to move from the primary database to the replicate database. You can use this information to monitor Replication Server performance, module heartbeat, replication health, and table-level quiesce. The results of each execution of rs_ticket is stored in a single row of the RS_TICKET_HISTORY table in the replicate database. You can query each row of the RS_TICKET_HISTORY table to obtain results of individual rs_ticket executions, or compare the results from different rows. The data stored in this table is not required to support replication and may be manually truncated.
The RS_TICKET_HISTORY table
is only available only in Replication Server version 15.1 and later.
