Mark Data for Replication

You can mark databases, tables, and functions for replication in MSA using sp_reptostandby, sp_setreptable, and sp_setrepproc.

Note: See the Replication Server Heterogeneous Replication Guide for non-ASE data servers.
When the database is marked by sp_reptostandby:
  • The RepAgent configuration parameter send warm standby xacts must be true.

  • User-defined stored procedures are not replicated unless they are marked individually using sp_setrepproc.

  • RepAgent sends DDL, system procedures, and transactions to the Replication Server. A database replication definition can filter them out at the Replication Server.

  • And you use table replication definitions and table subscriptions, you can send table data to both replicate databases and warm standby databases by setting the database connection parameter rep_as_standby on.

When the database is not marked by sp_reptostandby, DDL is not replicated for the marked tables and functions. See the Data Replication table for a summary of how data is replicated using the different system procedures for marking data for replication.

The table summarizes how data is replicated.

Data Replication

Data Marked By

Table and Function Subscriptions Only

Database Subscription Only

Table, Function, and Database Subscriptions Coexist

sp_setreptable and sp_setrepproc

  • Replicate marked data

  • Do not replicate DDL

  • Replicate marked data

  • Do not replicate DDL

  • Replicate marked data

  • Do not replicate DDL

sp_reptostandby

  • Check rep_as_standby

  • Do not replicate DDL

  • Replicate all data

  • Replicate DDL (optional)

  • Check rep_as_standby

  • Replicate DDL (optional)

sp_setreptable, sp_setrepproc, and sp_reptostandby

  • Check rep_as_standby

  • Do not replicate DDL

  • Replicate all data

  • Replicate DDL (optional)

  • Check rep_as_standby

  • Replicate DDL (optional)