From: Nitin Mehta Date: May 3 2012 11:21am Subject: Re: using the bin-log approach on the master side, how can I accomplish my replication objectives List-Archive: http://lists.mysql.com/mysql/227307 Message-Id: <1336044097.22099.YahooMailNeo@web161606.mail.bf1.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="1989420431-234463308-1336044097=:22099" --1989420431-234463308-1336044097=:22099 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Thanks for your kind words, Charles! It comes easily to you when you have e= xperienced it. I'm glad it worked for you.=0A=0A =0A=0A____________________= ____________=0A From: "Brown, Charles" =0ATo: Nitin Mehta <= ntnmht@stripped> =0ACc: "mysql@stripped" = =0ASent: Thursday, May 3, 2012 3:17 PM=0ASubject: RE: using the bin-log app= roach on the master side, how can I accomplish my replication objectives=0A= =0AHello Nitin,=0A=0APlease give Nitin a prize. What a quiet genius she i= s. Now, I get it. Now, I can see clearly.=0AI=E2=80=99ve tried it and it wo= rked.=0A=0AThanks so much.=0A=0AFrom: Nitin Mehta [mailto:ntnmht@stripped]= =0ASent: Wednesday, May 02, 2012 11:25 PM=0ATo: Brown, Charles=0ACc: mysql@= lists.mysql.com=0ASubject: Re: using the bin-log approach on the master sid= e, how can I accomplish my replication objectives=0A=0AHi Charles,=0AI beli= eve you would already have bin-log configured, is that right? If not, you n= eed to.=0ASecondly, 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 b= elow manner:=0Amysql> use db1;=0Amysql> update db2.tb2 ....=0AYou may be su= rprised to find that this update will not be recorded in master's bin-log i= f you have set "binlog-do-db=3Ddb2".=0ATo sum it up, if you're not very sur= e, simply enable bin-log on master and use "replicate-do-table" on slave. S= o in one word response to your question, no!=0AHope that helps!=0AAlso, ple= ase reply to all so the people, helping you, know about the status of your = problem.=0A=0A=0ARegards,=0A=0AFrom: "Brown, Charles" >=0ATo: Nitin Mehta >=0ASent: Thursday, May 3, 2012 9:27 AM=0ASubject: RE: using the bin-lo= g approach on the master side, how can I accomplish my replication objectiv= es=0A=0AHello Nitin,=0AHelp Me!=C2=A0 Using your approach, do I have to put= anything on=C2=A0 the master =E2=80=9Cmy.cnf=E2=80=9D.=0A=0AThanks=0A=0A= =0AFrom: Nitin Mehta [mailto:ntnmht@stripped]=0ASent: Wednesday, May 02, 2= 012 10:51 PM=0ATo: Brown, Charles; Rick James; a.smith@stripped; mysql@stripped=0ASu= bject: Re: using the bin-log approach on the master side, how can I accompl= ish my replication objectives=0A=0AI guess, it only makes things even more = simple.=0A=0AYou should use "replicate-do-table=3Ddb1.tb1" and so one in sl= ave's cnf to ensure that only this particular table gets replicated. Howeve= r, all the databases on master will get bin-logged and you may or may not w= ant to do that.=0A=0ASo making it even simpler:=0A=0Aon the slave:=0A=0Arep= licate-do-table=3Ddb1.tb1=0Areplicate-do-table=3Ddb2.tb2=0Areplicate-do-tab= le=3Ddb3.tb3=0AYou might want to have a look at :=0Ahttp://dev.mysql.com/do= c/refman/5.5/en/replication-options-slave.html#option_mysqld_replicate-do-t= able =0Ahttp://dev.mysql.com/doc/refman/5.5/en/replication-rules.html =0A= =0AHope this helps!=0A=0AFrom: "Brown, Charles" >=0ATo: Rick James >; "a.smith@stripped" >; "mysql@stripped" >=0ASent: Thur= sday, May 3, 2012 8:51 AM=0ASubject: using the bin-log approach on the mast= er side, how can I accomplish my replication objectives=0A=0AHello Rick,=0A= =0AI think I'll go with your recommendations - but help me here a little bi= t. Because all look fuzzy like a brain surgery. So make it simple and clean= for me.=0A=0A=0A=0AFor the sake of simplicity, here is what my master has:= =0A=0ADatabase: db1=0A=0ATables: db1tb1, db1tb2, db1tb3=0A=0A=0A=0ADatabase= : db2=0A=0ATables: db2tb1, db2tb2, db2tb3=0A=0A=0A=0ADatabase: db3=0A=0ATab= les: db3tb1, db3tb2, db3tb3=0A=0A=0A=0ANow, I would like to replicate only = these tables that belong to respective databases:=0A=0Adb1tb1, db2tb2, and = db3tb3=0A=0A=0A=0AMy question is: using the bin-log approach on the master = side, how can I accomplish my replication objectives? Help me=0A=0A=0A=0ABe= st regards and thanks=0A=0A=0A=0A=0A=0A=0A=0A******************************= **************=0AThis message is intended only for the use of the Addressee= and=0Amay contain information that is PRIVILEGED and CONFIDENTIAL.=0A=0AIf= you are not the intended recipient, you are hereby notified=0Athat any dis= semination of this communication is strictly prohibited.=0A=0AIf you have r= eceived this communication in error, please erase=0Aall copies of the messa= ge and its attachments and notify us=0Aimmediately.=0A=0AThank you.=0A*****= ***************************************=0A*********************************= ***********=0AThis message is intended only for the use of the Addressee an= d=0Amay contain information that is PRIVILEGED and CONFIDENTIAL.=0AIf you a= re not the intended recipient, you are hereby notified=0Athat any dissemina= tion of this communication is strictly prohibited.=0AIf you have received t= his communication in error, please erase=0Aall copies of the message and it= s attachments and notify us=0Aimmediately.=0AThank you.=0A*****************= ***************************=0A=0A=0A***************************************= *****=0AThis message is intended only for the use of the Addressee and=0Ama= y contain information that is PRIVILEGED and CONFIDENTIAL.=0A=0AIf you are = not the intended recipient, you are hereby notified=0Athat any disseminatio= n of this communication is strictly prohibited.=0A=0AIf you have received t= his communication in error, please erase=0Aall copies of the message and it= s attachments and notify us=0Aimmediately.=0A=0AThank you.=0A**************= ****************************** --1989420431-234463308-1336044097=:22099--