Changes an existing database replication definition.
alter database replication definition db_repdef with primary at srv.db {[not] replicate DDL | [not] replicate setname setcont | [not] replicate [{SQLDML | DML_options} [in table_list]} [with dsi_suspended]
setname ::= {tables | functions | transactions | system procedures}
setcont ::= [in ([owner1.] name1 [, [owner2.] name2 [, ...]])
If you omit the system procedures setname or include the not option, Replication Server does not replicate the system procedures.
If you omit tables, functions, or transactions setname or include the not option, Replication Server replicates all objects of the setname category.
When the database replication mode is set to any combination of UDIS, the RepAgent sends both individual log records and the information needed by Replication Server to build the SQL statement.
alter database replication definition rep_1C with primary at PDS.pdb not replicate tables in (table2) with dsi_suspended
alter database replication definition dbrepdef with primary at ds1.pdb1 replicate 'UD' in (tb1,tb2) go
When alter database replication definition is executed, Replication Server writes an rs_marker to the inbound queue. alter database replication definition does not take affect until the marker reaches the DIST, which gives the DIST time to incorporate the changes in the Database Subscription Resolution Engine (DSRE).
Altering a database replication definition may desynchronize the primary and replication databases. See the Replication Server Administration Guide Volume 1 for instructions for resynchronizing databases.
SQL statement replication
If you do not specify a filter in your replication definition, the default is the not replicate clause. Apply alter database replication definition to change the SQLDML filters. You can either specify one or multiple SQLDML filters in a replicate clause.
For more information about SQL statement replication see create database replication definition.