SQL Statements for Controlling Replica Servers • REPLICATE_DO_TABLE : Include updates based on table name. Equivalent to  --replicate-do- table . • REPLICATE_IGNORE_TABLE : Exclude updates based on table name. Equivalent to  --replicate- ignore-table . • REPLICATE_WILD_DO_TABLE : Include updates based on wildcard pattern matching table name. Equivalent to  --replicate-wild-do-table . • REPLICATE_WILD_IGNORE_TABLE : Exclude updates based on wildcard pattern matching table name. Equivalent to  --replicate-wild-ignore-table . • REPLICATE_REWRITE_DB : Perform updates on replica after substituting new name on replica for specified database on source. Equivalent to  --replicate-rewrite-db . The precise effects of  REPLICATE_DO_DB  and  REPLICATE_IGNORE_DB  filters are dependent on whether statement-based or row-based replication is in effect. See Section 17.2.5, “How Servers Evaluate Replication Filtering Rules” , for more information. Multiple replication filtering rules can be created in a single  CHANGE REPLICATION FILTER  statement by separating the rules with commas, as shown here: Issuing the statement just shown is equivalent to starting the replica  mysqld  with the options  -- replicate-do-db=d1 --replicate-ignore-db=d2 . On a multi-source replica, which uses multiple replication channels to process transaction from different sources, use the  FOR CHANNEL  channel  clause to set a replication filter on a replication channel: This enables you to create a channel specific replication filter to filter out selected data from a source. When a  FOR CHANNEL  clause is provided, the replication filter statement acts on that replication channel, removing any existing replication filter which has the same filter type as the specified replication filters, and replacing them with the specified filter. Filter types not explicitly listed in the statement are not modified. If issued against a replication channel which is not configured, the statement fails with an ER_SLAVE_CONFIGURATION  error. If issued against Group Replication channels, the statement fails with an  ER_SLAVE_CHANNEL_OPERATION_NOT_ALLOWED  error. On a replica with multiple replication channels configured, issuing  CHANGE REPLICATION FILTER  with no  FOR CHANNEL  clause configures the replication filter for every configured replication channel, and for the global replication filters. For every filter type, if the filter type is listed in the statement, then any existing filter rules of that type are replaced by the filter rules specified in the most recently issued statement, otherwise the old value of the filter type is retained. For more information see Section 17.2.5.4, “Replication Channel Based Filters” . If the same filtering rule is specified multiple times, only the  last  such rule is actually used. For example, the two statements shown here have exactly the same effect, because the first  REPLICATE_DO_DB  rule in the first statement is ignored: 2758 CHANGE REPLICATION FILTER REPLICATE_DO_DB = (db1, db2), REPLICATE_DO_DB = (db3, db4); CHANGE REPLICATION FILTER REPLICATE_DO_DB = (db3, db4); CHANGE REPLICATION FILTER REPLICATE_DO_DB = (d1), REPLICATE_IGNORE_DB = (d2); CHANGE REPLICATION FILTER REPLICATE_DO_DB = (d1) FOR CHANNEL channel_1;