Thanks for your kind words, Charles! It comes easily to you when you have experienced it. I'm glad it worked for you.
________________________________ From: "Brown, Charles" <cbr...@bmi.com> To: Nitin Mehta <ntn...@yahoo.com> Cc: "mysql@lists.mysql.com" <mysql@lists.mysql.com> Sent: Thursday, May 3, 2012 3:17 PM Subject: RE: using the bin-log approach on the master side, how can I accomplish my replication objectives Hello Nitin, Please give Nitin a prize. What a quiet genius she is. Now, I get it. Now, I can see clearly. I’ve tried it and it worked. Thanks so much. From: Nitin Mehta [mailto:ntn...@yahoo.com] Sent: Wednesday, May 02, 2012 11:25 PM To: Brown, Charles Cc: mysql@lists.mysql.com Subject: Re: using the bin-log approach on the master side, how can I accomplish my replication objectives Hi Charles, I believe you would already have bin-log configured, is that right? If not, you need to. Secondly, If you think the bin-log generated for the entire stack of databases/schemas is too big, you may want to restrict it using "binlog-do-db" BUT that may create problem if you have any DMLs which run in the below manner: mysql> use db1; mysql> update db2.tb2 .... You may be surprised to find that this update will not be recorded in master's bin-log if you have set "binlog-do-db=db2". To sum it up, if you're not very sure, simply enable bin-log on master and use "replicate-do-table" on slave. So in one word response to your question, no! Hope that helps! Also, please reply to all so the people, helping you, know about the status of your problem. Regards, From: "Brown, Charles" <cbr...@bmi.com<mailto:cbr...@bmi.com>> To: Nitin Mehta <ntn...@yahoo.com<mailto:ntn...@yahoo.com>> Sent: Thursday, May 3, 2012 9:27 AM Subject: RE: using the bin-log approach on the master side, how can I accomplish my replication objectives Hello Nitin, Help Me! Using your approach, do I have to put anything on the master “my.cnf”. Thanks From: Nitin Mehta [mailto:ntn...@yahoo.com] Sent: Wednesday, May 02, 2012 10:51 PM To: Brown, Charles; Rick James; a.sm...@ukgrid.net<mailto:a.sm...@ukgrid.net>; mysql@lists.mysql.com<mailto:mysql@lists.mysql.com> Subject: Re: using the bin-log approach on the master side, how can I accomplish my replication objectives 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" <cbr...@bmi.com<mailto:cbr...@bmi.com>> To: Rick James <rja...@yahoo-inc.com<mailto:rja...@yahoo-inc.com>>; "a.sm...@ukgrid.net<mailto:a.sm...@ukgrid.net>" <a.sm...@ukgrid.net<mailto:a.sm...@ukgrid.net>>; "mysql@lists.mysql.com<mailto:mysql@lists.mysql.com>" <mysql@lists.mysql.com<mailto:mysql@lists.mysql.com>> 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. ******************************************** ******************************************** 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. ******************************************** ******************************************** 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. ********************************************
