The connection profile creates three tables in Sybase IQ replicate database to support Replication Server operations:
rs_threads, which is used by Replication Server to detect deadlocks and to perform transaction serialization between parallel DSI threads. An entry is updated in this table each time a transaction is started and more than one DSI thread is defined for a connection.
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-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, 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 to compare the results from different rows. The data may be manually truncated.
