I guess, it only makes things even more simple.
You should use "replicate-do-table=db1.tb1" and so one in slave's cnf to ensure that
only this particular table gets replicated. However, all the databases on master will get
bin-logged and you may or may not want to do that.
So making it even simpler:
on the slave:
replicate-do-table=db1.tb1
replicate-do-table=db2.tb2
replicate-do-table=db3.tb3
You might want to have a look at :
http://dev.mysql.com/doc/refman/5.5/en/replication-options-slave.html#option_mysqld_replicate-do-table
http://dev.mysql.com/doc/refman/5.5/en/replication-rules.html
Hope this helps!
________________________________
From: "Brown, Charles" <CBrown@stripped>
To: Rick James <rjames@stripped>; "a.smith@stripped"
<a.smith@stripped>; "mysql@stripped" <mysql@stripped>
Sent: Thursday, May 3, 2012 8:51 AM
Subject: using the bin-log approach on the master side, how can I accomplish my
replication objectives
Hello Rick,
I think I'll go with your recommendations - but help me here a little bit. Because all
look fuzzy like a brain surgery. So make it simple and clean for me.
For the sake of simplicity, here is what my master has:
Database: db1
Tables: db1tb1, db1tb2, db1tb3
Database: db2
Tables: db2tb1, db2tb2, db2tb3
Database: db3
Tables: db3tb1, db3tb2, db3tb3
Now, I would like to replicate only these tables that belong to respective databases:
db1tb1, db2tb2, and db3tb3
My question is: using the bin-log approach on the master side, how can I accomplish my
replication objectives? Help me
Best regards and thanks
********************************************
This message is intended only for the use of the Addressee and
may contain information that is PRIVILEGED and CONFIDENTIAL.
If you are not the intended recipient, you are hereby notified
that any dissemination of this communication is strictly prohibited.
If you have received this communication in error, please erase
all copies of the message and its attachments and notify us
immediately.
Thank you.
********************************************
