Oracle 5.0 Reference Manual page 1511

Replicating Different Databases to Different Slaves
to help spread the load during data analysis. A sample of this layout is shown in
Replication to Replicate Databases to Separate Replication
Figure 16.2. Using Replication to Replicate Databases to Separate Replication Slaves
You can achieve this separation by configuring the master and slaves as normal, and then limiting the
binary log statements that each slave processes by using the
configuration option on each slave.
Important
You should not use
affects vary according to the database that is currently selected.
For example, to support the separation as shown in
Databases to Separate Replication
before executing
START
• Replication slave 1 should use --replicate-wild-do-table=databaseA.%.
• Replication slave 2 should use --replicate-wild-do-table=databaseB.%.
• Replication slave 3 should use --replicate-wild-do-table=databaseC.%.
Each slave in this configuration receives the entire binary log from the master, but executes only those
events from the binary log that apply to the databases and tables included by the
[1459]
wild-do-table
If you have data that must be synchronized to the slaves before replication starts, you have a number
of choices:
• Synchronize all the data to each slave, and delete the databases, tables, or both that you do not
want to keep.
• Use to create a separate dump file for each database and load the appropriate dump file
mysqldump
on each slave.
• Use a raw data file dump and include only the specific files and databases that you need for each
slave.
Note
This does not work with
innodb_file_per_table
--replicate-do-db
Slaves", you should configure each replication slave as follows,
SLAVE:
option in effect on that slave.
InnoDB
1491
Slaves".
--replicate-wild-do-table
[1457] for this purpose, since its
Figure 16.2, "Using Replication to Replicate
databases unless you use
[1241].
Figure 16.2, "Using
[1459]
--replicate-