views:

205

answers:

4

I want to do that using a code and not using a tool like "MySQL Migration Toolkit". The easiest way I know is to open a connection (using MySQL connectors) to DB1 and read its data. Open connection to DB2 and write the data to it. Is there a better/easiest way ?

+2  A: 

The FEDERATED storage engine? Not the fastest one in the bunch, but for one time, incidental, or small amounts of data it'll do. That is assuming you're talking about 2 SERVERS. With 2 databases on one and the same server it'll simply be:

INSERT INTO databasename1.tablename SELECT * FROM databasename2.tablename;
Wrikken
Thanks a lot, I'm not sure yet If the 2 databases are on the same server or not.
Morano88
+1  A: 

You can use mysqldump and mysql (the command line client). These are command line tools and in the question you write you don't want to use them, but still using them (even by running them from your code) is the easiest way; mysqldump solves a lot of problems.

You can make selects from one database and insert to the other, which is pretty easy. But if you need also to transfer the database schema (create tables etc.), it gets little bit more complicated, which is the reason I recommend mysqldump. But lot of PHP-MySQL-admin tools also does this, so you can use them or look at their code.

Or maybe you can use MySQL replication.

Messa
Will this (selects, inserts) work if the two databases are on 2 different servers ?No I just want to migrate data, not table creations .. etc.
Morano88
Yes, you will have tvo connections - for each server one - in one connection you run SELECT, then in the other INSERT with the data that returned from that SELECT.
Messa
A: 

If you enabled binary logging on your current server (and have all the bin logs) you can setup replication for the second server

desertwebdesigns
+1  A: 

First I'm going to assume you aren't in a position to just copy the data/ directory, because if you are then using your existing snapshot/backup/restore will probably suffice (and test your backup/restore procedures into the bargain).

In which case, if the two tables have the same structure generally the quickest, and ironically the easiest approach will be to use SELECT...INTO OUTFILE... on one end, and LOAD DATA INFILE... on the other.

See http://dev.mysql.com/doc/refman/5.1/en/load-data.html and .../select.html for definitive details.

For trivial tables the following will work:

SELECT * FROM mytable INTO OUTFILE '/tmp/mytable.csv' FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"' ESCAPED BY '\\' LINES TERMINATED BY '\n' ;

LOAD DATA INFILE '/tmp/mytable.csv' INTO TABLE mytable FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"' ESCAPED BY '\\' LINES TERMINATED BY '\n' ;

We have also used FIFO's to great effect to avoid the overhead of actually writing to disk, or if we do need to write to disk for some reason, to pipe it through gzip.

ie.

mkfifo /tmp/myfifo gzip -c /tmp/myfifo > /tmp/mytable.csv.gz & ... SELECT... INTO OUTFILE '/tmp/myfifo' ..... wait

gunzip -c /tmp/mytable.csv.gz > /tmp/myfifo & ... LOAD DATA INFILE /tmp/myfifo ..... wait

Basically, one you direct the table data to a FIFO you can compress it, munge it, or tunnel it across a network to your hearts content.

Recurse
Thanks, though it is in the dev.mysql manual but it is not working proberly. It is giving me this error :You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '\n'' at line 1)It is not accepting '\n' .. why ?
Morano88
Stack Overflow corrupted the sample query. In the source, the slash in the ESCAPED BY clause was escaped, but the escape was lost when converted to html. Sorry about that, I hadn't noticed the corruption - I've fixed it above.
Recurse