For ASE: Primary database initialization (command pdb_init) verifies the database, and it will be configured with command sp_reptostandby pdb,'ALL'. This automatically marks all tables for replication, as well as all DDL commands.
For ASE only, individual tables can not be marked or
unmarked when the primary database is configured with sp_reptostandby (which
is the default ASE setting for a Mirror Activator environment).
For Microsoft SQL Server and Oracle: The individual tables to be replicated must be marked, either explicitly using the pdb_setreptable command, or automatically during pdb_init processing when configuration parameter pdb_automark_tables is set to true.
To replicate transactions that affect the data in a table in the primary database, that table must be marked for replication, and replication must be enabled for the marked table.
By default, Mirror Replication Agent creates a replication
definition in Replication Server for each table that is explicitly
marked for replication. Also, Mirror Replication Agent creates a
replication definition for each table created during replication
(by reading the DDL command). If this is not the default behavior
desired, you can turn off automatic replication definition creation using
the pdb_auto_create_repdefs configuration
parameter.
WARNING!
For Oracle and Microsoft SQL Server: The default value for the pdb_auto_create_repdefs configuration property is true, which will cause a replication definition to be created for each table that is marked for replication during processing of the ra_init command. If you have thousands of tables, this may result in significant additional execution time. To avoid this additional execution time, set the pdb_auto_create_repdefs configuration property to false before invoking the ra_init command. When ra_init execution completes and before replicating, execute the rs_create_repdef all command to create your replication definitions.
For ASE: While the database may be marked for replication, individual tables are not marked, so individual replication definitions are not created when the ra_init command is executed, regardless of the setting of the pdb_auto_create_repdefs configuration property.
Marking a table can be separate from enabling replication for that table. If the value of the pdb_dflt_object_repl parameter is true, replication is enabled automatically at the time a table is marked. For more information, see “Enabling and disabling replication for marked tables”.
When a table is marked for replication with the log-based Mirror Replication Agent for Oracle, the Mirror Replication Agent does the following:
Connects to the RASD
Records the mark status for the table in the RASD Article for that table.
When a table is marked, any subsequent operations that affect the data in that table are replicated.
When a table is marked for replication with the log-based Mirror Replication Agent for Microsoft SQL Server, Mirror Replication Agent logs in to the primary database and executes commands to turn on logging of changes in the Microsoft SQL Server transaction log.
When a table marked for replication is unmarked with the log-based Mirror Replication Agent for Microsoft SQL Server, Mirror Replication Agent logs in to the primary database and executes commands to turn off logging of changes in the Microsoft SQL Server transaction log.
