Re: replicate-rewrite-db

On Fri, Apr 4, 2008 at 6:30 AM, Shanmugam, Dhandapani < [EMAIL PROTECTED]> wrote: Hi, Hi, > > Any idea wat replicate-rewrite-db does with example.. > > > > It takes statements for one database, and rewrites them into another. An example of the syntax would be this li

replicate-rewrite-db

Hi, Any idea wat replicate-rewrite-db does with example..

Re: To replicate or not to replicate that is the question

> I need to put a read-only copy of a single table on a database another > server so remote customers can have read access to it. I use SQLYob Job Agent to synchronise two MySQL databases. See http://www.webyog.com/en/ for more information. I use SSH to so port forwarding from one box to the

Re: To replicate or not to replicate that is the question

This is something I do with replication. You can replicate a list of tables, see the 'replicate_do_table' config option. Then you can euse the 'read_only' option. Replication still works but nothing else. But it would give you more options by using GRANT instead of &

To replicate or not to replicate that is the question

I need to put a read-only copy of a single table on a database on another server so remote customers can have read access to it. I built a new MySQL server and placed in my DMZ. I can use SSH forwarding to access it from outside. Now I need to get a copy of the table from my internal MySQL server t

Re: How to replicate a timestamp field

In news:[EMAIL PROTECTED], Bruno Rodrigues Silva <[EMAIL PROTECTED]> wrote: > this field (The master is dep= loyed Europe and the slave in Brazil). > The time of fly to replicate the que= ry that leave the master and go > to slave can be more than 1 second. Therefo= re, whe

How to replicate a timestamp field

Hello. I know that when a timestamp field has "default current_timestamp on update current_timestamp", it will be updated for each update. Question: I have a slave server which replicate this field (The master is deployed Europe and the slave in Brazil). The time of fly to rep

Re: Easiest Way To Replicate DB

I am doing tests so I want to easy take my DB and make a full copy of it into a test db everytime I want to test something against the non-produciton version of DB. What is the easiest way to do this. So I have a DB called "backlog" and I want to copy it's structure and data into "backlog_test"

Easiest Way To Replicate DB

I am doing tests so I want to easy take my DB and make a full copy of it into a test db everytime I want to test something against the non-produciton version of DB. What is the easiest way to do this. So I have a DB called "backlog" and I want to copy it's structure and data into "backlog_test"

Re: Need to replicate my DB on 5 branches into 1 DB at HO - Urgent

If u need this in urgent, i think my suggestion may help you. try to do replication in this way Branch-A will be update in Branch-B and Branch-B will update in Branch-C . Branch-E(which got total data of A,B,C,D) will update in Main Office.

Re: Need to replicate my DB on 5 branches into 1 DB at HO - Urgent

On 5/22/06, Winanjaya - CBN <[EMAIL PROTECTED]> wrote: > Dear Expert, > > I am very new to MySQL replication, I need to replicate my DB on 5 branches into 1 DB at Head Office. > > eg. > > MyDB at Branch A need to be replicated to MyDB at Head Office > MyDB at Bra

Re: Need to replicate my DB on 5 branches into 1 DB at HO - Urgent

MySQL replication, I need to replicate my DB on 5 branches into 1 DB at Head Office. eg. MyDB at Branch A need to be replicated to MyDB at Head Office MyDB at Branch B need to be replicated to MyDB at Head Office MyDB at Branch C need to be replicated to MyDB at Head Office MyDB at Branch D need

Need to replicate my DB on 5 branches into 1 DB at HO - Urgent

Dear Expert, I am very new to MySQL replication, I need to replicate my DB on 5 branches into 1 DB at Head Office. eg. MyDB at Branch A need to be replicated to MyDB at Head Office MyDB at Branch B need to be replicated to MyDB at Head Office MyDB at Branch C need to be replicated to MyDB at

Re: --replicate-rewrite-db fails when attempting to drop a table

gt; leave it this way, they therefore asked if it was possible to replicate to a > different database > name, e.g. livedb_backup. > > I suggested the use of the --replicate-rewrite-db option. > > When I set this up and tested it I decided to create a new table and then >

--replicate-rewrite-db fails when attempting to drop a table

the master and the customer wants to leave it this way, they therefore asked if it was possible to replicate to a different database name, e.g. livedb_backup. I suggested the use of the --replicate-rewrite-db option. When I set this up and tested it I decided to create a new table and then d

RE: When to cluster vs. replicate

-Original Message- From: Richard Reina [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 07, 2004 11:30 AM To: [EMAIL PROTECTED] Subject: When to cluster vs. replicate For some time I have been considering replication for added redundancy so that should something happen to the server

When to cluster vs. replicate

Data from my business's transactions are stored in a few dozen tables in about 5 databases. Right now the MySQL server with dual RAID 0 80 gig drives. So far the data which stores about 4 years worth of data only takes up 1 gig. There are about 4 or five work stations that store data on this serv

Re: long update query does not replicate correctly (cont.)

. Yes. I have recently add the following line to the slave's my.cnf file: replicate-wild-do-table=abe_exp.% There are no more replication rules in that file. Both tables included in the multitable update were in this database (abe_exp). So this is a bug. I suggest then that you file a bug rep

Re: long update query does not replicate correctly (cont.)

have recently add the following line to the slave's my.cnf file: replicate-wild-do-table=abe_exp.% There are no more replication rules in that file. Both tables included in the multitable update were in this database (abe_exp). So this is a bug. -- ./ premax ./ [EMAIL PROTECTED] ./ koniec i

Re: long update query does not replicate correctly (cont.)

Przemyslaw Popielarski wrote: I'm executing on master a long and complicated query such: UPDATE (lots of tables, lots of LEFT JOIN) SET ... WHERE . Okey, I simplified the query to: - UPDATE tKsidata, tKsiabeksiazki SET tKsidata.STAN_REALNY=tKsiabeksiazki.STAN WHERE tKsidat

Re: long update query does not replicate correctly (cont.)

> I'm executing on master a long and complicated query such: > UPDATE (lots of tables, lots of LEFT JOIN) SET ... WHERE . Okey, I simplified the query to: - UPDATE tKsidata, tKsiabeksiazki SET tKsidata.STAN_REALNY=tKsiabeksiazki.STAN WHERE tKsidata.ksi='0815120877' and tKs

long update query does not replicate correctly

I'm executing on master a long and complicated query such: UPDATE (lots of tables, lots of LEFT JOIN) SET ... WHERE . The query updates i.e. 3816 rows. The query DOES replicate do master's and slave's binary log. But it DOES NOT execute on slave. 3816 rows are not updated on s

Re: SELECT queries on replicate DB server

Thanks, that is a really good answer. Raises a bunch more questions but they're good ones. Jim Grill wrote: My question is: Why would they deem it necessary to use yet a third server? Could it be because the main server and the main slave are constantly being updated and they wouldn't want to ov

Re: SELECT queries on replicate DB server

> > My question is: > Why would they deem it necessary to use yet a third server? Could it > be because the main server and the main slave are constantly being > updated and they wouldn't want to overload the main slave(which > is not on as high a horsepower of a box I know for a fact). Could it

SELECT queries on replicate DB server

the website where all the queries are select only. So what was done was to replicate the affected tables on yet a third server. Now we're set up so that when that block of code is invoked, it connects the third db server to take the load off the main one, knowing ahead of time that there

Re: Problem with Replication - Slave Option replicate-ignore-tabl e and replicate-wild-ignore-table

Hi, I have had similar problems with "do-table", but never succeded finalizing my bug-report. I have added (on master) ... "SET SQL_LOG_BIN = 0" as start of each action where not to replicate data "SET SQL_LOG_BIN = 1" as start of each action where to replicate

Re: Problem with Replication - Slave Option replicate-ignore-tabl e and replicate-wild-ignore-table

Yes. I also tried that. Are there any other suggestions? What's about the different sections in my.cnf? Should these statements beeing written under [mysqld_safe], too? Victor Pendleton wrote: In the slave's my.cnf have you tried just expliciting statement what tables to ignore? replic

RE: Problem with Replication - Slave Option replicate-ignore-tabl e and replicate-wild-ignore-table

In the slave's my.cnf have you tried just expliciting statement what tables to ignore? replicate-ignore-table=db.table1 replicate-ignore-table=db.table2 ... replicate-ignore-table=db.tablen And remove the other statements? -Original Message- From: Mike Lohman To: [EMAIL PROTECTED]

Problem with Replication - Slave Option replicate-ignore-table and replicate-wild-ignore-table

om/mysql/153722 I tried several times to delete the master.info on the slave and restart the slave-server. Replication allways got up to work again. But the replicate-wild and replicate-ignore-table entries are never used. Please help. Part of the slave- my.cnf, concerning replication: master-host

Re: --replicate* question

Egor Egorov <[EMAIL PROTECTED]> wrote: > Chua Choon Keng <[EMAIL PROTECTED]> wrote: >>> What about using binlog-do-db=database_name >> option? In this case only updates will be logged if >> the current database is database_name >> >> What if I only

Re: --replicate* question

Chua Choon Keng <[EMAIL PROTECTED]> wrote: >> What about using binlog-do-db=database_name > option? In this case only updates will be logged if > the current database is database_name > > What if I only wish to replicate a few tables of a > database? Using binlog-do-db

Re: --replicate* question

> What about using binlog-do-db=database_name option? In this case only updates will be logged if the current database is database_name What if I only wish to replicate a few tables of a database? Using binlog-do-db=database_name does limit to this particular database but there is no bin

Re: --replicate* question

Chua Choon Keng <[EMAIL PROTECTED]> wrote: > Dear all, > > I am new to mysql replication. I know how to use > the --replicate* options but I would like to know > whether the options act as filter on the master or > on the slave... On the slave. > > From the

--replicate* question

Dear all, I am new to mysql replication. I know how to use the --replicate* options but I would like to know whether the options act as filter on the master or on the slave... >From the documentation, it says: "The --replicate-* rules are evaluated as follows to determine whether a s

Re: --replicate-do-table usage example

Andrew Pasetti wrote: I'm a bit new to mysql replication. Can someone please explain how to implement the --replicate-do-table start up option? Replication is up and running, but I would like to limit the replication to just two specific tables in one database only. Using mysql v4.0.18 Linu

--replicate-do-table usage example

I'm a bit new to mysql replication. Can someone please explain how to implement the --replicate-do-table start up option? Replication is up and running, but I would like to limit the replication to just two specific tables in one database only. Using mysql v4.0.18 Linux/x86 Your advice wi

Can 64-bit MySQL replicate to 32-bit MySQL?

Are the binary logs in the same format? Are data types the same? Thanks in advance, David

Re: Ignor table in replication: replicate-wild-ignore-table

At 22:37 + 12/19/03, Mike S wrote: I want to stop replication for one table in the database. According to the mysql documentation: I need to add the parameter (replicate-wild-ignore-table ) to the my.cnf file. I have some question. #1 In what database I should made the change to my.cnf

Ignor table in replication: replicate-wild-ignore-table

I want to stop replication for one table in the database. According to the mysql documentation: I need to add the parameter (replicate-wild-ignore-table ) to the my.cnf file. I have some question. #1 In what database I should made the change to my.cnf? Slave or Master? #2 Than I should restart

replicate-ignore(d)-table continues to replicate

Hi, We are using the binary distribution of mysql for solaris 9 64bit on 2 machines that are replicating to each other for redundancy: mysql-standard-4.0.14-sun-solaris2.9-sparc-64bit I am successfully able use replicate-ignore-db=blah to stop replication on a database, however when I specify

Re: Partial replicate InnoDB -> MyISAM

see below... - Original Message - From: "Chris Nolan" <[EMAIL PROTECTED]> To: "Jon Hancock" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Tuesday, October 28, 2003 10:49 AM Subject: Re: Partial replicate InnoDB -> MyISAM > Hmm >

Re: Partial replicate InnoDB -> MyISAM

Re: MySQL/InnoDB-4.0.16 is released + sneak peek of > 4.1.1". > > I may want to have one MySQL server as the Read only "Search" server. If I > did this and I have all InnoDB table on my Master, then could I replicate > only certain columns into the MyISAM slave ? > &

Partial replicate InnoDB -> MyISAM

This thread started as "Re: MySQL/InnoDB-4.0.16 is released + sneak peek of 4.1.1". I may want to have one MySQL server as the Read only "Search" server. If I did this and I have all InnoDB table on my Master, then could I replicate only certain columns into the MyISA

replicate

I don't really think this can be done, but I figured that I would ask anyways I want 3 mysql server running (A,B and C) I want only one table from A to replicate to B and I want all of B but the one table from A to replicate to C and I want C to replicate back to B -Michael "

re: binlog-ignore-db & replicate-ignore-db problem

in the current database. > In the other hand on my repication in my.cnf I have: > replicate-ignore-db=access > > which is supposed to make the repication to not replicate for db > "access", but again it doesn't do this. The same. If you specify replicate-ignore-db=acce

binlog-ignore-db & replicate-ignore-db problem

ter not to log updates for db "access", but but it doesn't, and I can see it examinig my bin log with "mysqlbinlog" In the other hand on my repication in my.cnf I have: replicate-ignore-db=access which is supposed to make the repication to not replicate for db "access

replicate-rewrite-db

I have the same db on master and slave and I want to use replicate-rewrite-db to change the replicating name of this db on the slave. Slave my.cnf: --- [mysqld] datadir=/var/lib/mysql socket=/tmp/mysql.sock master-host=master.company.com master-user=repl master

re: syntax problem with replicate-rewrite-db

David, Tuesday, November 19, 2002, 5:20:23 PM, you wrote: DN> (sorry if this is a duplicate -- I don't think the original made it) DN> Running mysql 3.23.53-max binary on a RedHat 7.2 based server. Replication DN> is working fine, but I'm running into errors with the repl

syntax problem with replicate-rewrite-db

Hi All, (sorry if this is a duplicate -- I don't think the original made it) Running mysql 3.23.53-max binary on a RedHat 7.2 based server. Replication is working fine, but I'm running into errors with the replicate-rewrite-db directive. Here's a snippet from my my.cnf fi

syntax problem with replicate-rewrite-db

Hi All, Running mysql 3.23.52-max binary on a RedHat 7.2 based server. Replication is working fine, but I'm running into errors with the replicate-rewrite-db directive. Here's a snippet from my my.cnf file on the slave: master-port = 3306 replicate-rewrite-db=mysql->maste

Re: replicate-do-table and related

ed query itself > and slave will read that file, and depends on your slave configuration which tables > you'll only want to replicate the query. > (--replicate-do-table=.) > > check also your master.info file > > to check this configuration ... > watch the hostname.err

Re: replicate-do-table and related

Pada Mon, 11 Nov 2002 01:04:10 +0300 Mike Blazer <[EMAIL PROTECTED]> menulis: > And replication... well, it kinda works, I see that voy88-relay-bin.001 > grows - but it does not change my tables. So, I'm assuming that it does > not understand replicate-do-table rules. &

replicate-do-table and related

= \ --master-user=mylogin \ --master-password=mypwd \ --master-port=3306 \ --server-id=88 \ --master-connect-retry=60 \ ... And In fact that's ok that master logs everything, I'm planning to deploy a mirror later. But for *this* slave I want to replicate onl

Re: Is it possible to replicate just a couple of tables insteadof the whole database

Ralf Koellner wrote: > Hi, > > Is it possible to replicate just some tables instead of a whole mysql > database? A replication of the whole database would be not necessary in > my case. It would be a one-way replication (means slave won't update > master). You can use

re: Re: Is it possible to replicate just a couple of tables instead of the whole database

Ralf, Monday, October 28, 2002, 11:48:22 PM, you wrote: RK> Is it possible to replicate just some tables instead of a whole mysql RK> database? A replication of the whole database would be not necessary in RK> my case. It would be a one-way replication (means slave won't upda

Re: Is it possible to replicate just a couple of tables insteadof the whole database

Hi, Is it possible to replicate just some tables instead of a whole mysql database? A replication of the whole database would be not necessary in my case. It would be a one-way replication (means slave won't update master). Furthermore: Is there a cheep tool taking care of that (wi

Selecting databases to replicate ?

Bonjour, I configured two of my servers for replication. On the master I added : log-bin master-host = xxx.. master-user = x master-password = x master-port = 3306 server-id = 14 master-connect-retry=10 binlog-do-db=db1 binlog-do-db=db2 binlog-do-db

Single DB trying to replicate to itself?

RH 7.2. mysql-3.23.44 I have a single server running mysql. I have added one database I use. For some unknown reason, it appears that mysql is trying to replicate to something, failing and causing mysql to stop responding almost daily. /etc/my.cnf has no reference to any master/slave or

replicate-rewrite-db

Hello (Post 2) Has anyone got replicate-rewrite-db (a my.cnf entry) to work. I have replication running fine, however the rewrite doesn't work. I just want to know whether I should persist or if there is something special people had to do to get it working. I have heard / read a few p

replicate-rewrite-db

Hello Has anyone got replicate-rewrite-db (a my.cnf entry) to work. I have replication running fine, however the rewrite doesn't work. I just want to know whether I should persist or if there is something special people had to do to get it working. I have heard / read a few people saying

Re: replicate-ignore-table

On Wed, Feb 06, 2002 at 10:02:02AM -0600, Todd Newbold wrote: > Hi everyone, > >When using replicate-ignore-table in mysql, does filtering happen > before or after transmission from the master to the slave? Is the directive on the slave? If so, that's where it happ

replicate-ignore-table

Hi everyone, When using replicate-ignore-table in mysql, does filtering happen before or after transmission from the master to the slave? Thanks - Before posting, please check: http://www.mysql.com/manual.php (the

replicate-wild-ignore under mutual master-slave relation

Hello, I have two servers under a mutual master-slave relationship. I need to ignore certain databases when replicating. I tried to use replicate-ignore-db but according to the MySQL manual this won't work for cross database updates. The manual suggests using replicate-wild-ignore-table in

replicate-do-table

Hello everyone, How does mysql replication handle the replicate-do-table config option? Does the binlog get filtered before transmission, or once data is received by the slave? Thanks Todd - Before posting, please

How to ignore SQL errors on replicate

Hello, I use 2 MySQL-3.23.41 servers. These serers do mutual replication. I have problem with one table. In the table is a UNIQUE field. This field is used by a RADIUS server which sometimes wants to store 2 (or more) rows with the same ID (which is unique). For the master server it is

Re: Please help me , about mysql replicate!

On Fri, Aug 31, 2001 at 05:44:11PM +0800, Wang Aocheng wrote: > Dear All, > > I have a question: > > How can build multi-master-host? > > I have 3 mysql hosts,I want to use mysql data replicate. thanks! And you want all 3 to be masters? If so, you need t

Please help me , about mysql replicate!

Dear All, I have a question: How can build multi-master-host? I have 3 mysql hosts,I want to use mysql data replicate. thanks! wac - Before posting, please check: http://www.mysql.com/manual.php (the

Feature Request: replicate-ignore-table for Master *before* killing updatelog!

Hi, it would be nice to have a replicate-ignore-table for the Master also! It works fine, but if one has to replicate only certain tables of a db it would be good to have this. It is not enough to have this on slave only, because we do not want to send the data of whole databases across the

Is there a way to merge/replicate between MySQL and MSSQL?

I have a production MS SQL server and want to keep a copy on a MySQL DB on the webserver (for speed and redundancy). I have searched the archives, docs, and altavista and cannot find exactly what I am looking for. Ultimately, I would like to be able to have the databases merge/replicate between