The only significant intrusions or impacts to the Microsoft SQL Server replicate database are the database objects created by the hds_msss_setup_for_replicate.sql script to support Replication Server replicate database operations.
The hds_msss_setup_for_replicate.sql script creates three tables in the replicate database to support Replication Server operations:
RS_INFO, which contains information about the sort order and character set used by the replicate database
Verify that the insert statements
for the RS_INFO table (in the hds_msss_setup_for_replicate.sql script)
specify the proper character set and sort order for your Microsoft
SQL Server 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, which contains information about replicated transactions 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-Sybase 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, which contains the execution results of Replication Server command rs_ticket.The rs_ticket command can be issued 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 in Replication Server release 15.1 and later.
