rs_ticket stored procedure version 2

rs_ticket is now on its version 2 and provides support for non-ASE databases. You can use rs_ticket stored procedure without additional configuration and administration. Tickets are automatically inserted into the rs_ticket_history table, which is located in the replicate database. Tickets are sharable among multiple applications, where they are issued without obstruction from tickets of other applications.

With rs_ticket version 2, more ticket information is provided for better usability, such as the Replication Server Interface (RSI) timestamp, which you can retrieve without writing complex queries. You can directly query the rs_ticket_history table for Replication Server performance. If the computer time or tickets are not synchronized across multiple time zones, you can change the timestamp columns to adjust the ticket date.

The earlier version of rs_ticket has been renamed rs_ticket_v1. To use the earlier version, alter rs_ticket_report function string with your old content or with the default, exec rs_ticket_report ?rs_ticket_param!param?.

NoteIf you previously disabled dsi_rs_ticket_report and upgraded to Replication Server 15.1, the dsi_rs_ticket_report setting is reenabled after the upgrade process has finished.

These are the format changes that have been made to rs_ticket:

See the Replication Server Reference Manual for detailed information about using rs_ticket version 2.