The above only makes sense if you are talking different databases on the servers you are migrating to. If they are all mySQL then definitely go the dump file route.
D
[EMAIL PROTECTED] wrote:
Quoting Colin Wetherbee <[EMAIL PROTECTED]>:
Ron Savage said:
On Fri, 3 Oct 2003 13:44:53 +0300, [EMAIL PROTECTED] wrote:
I want to create a migration tool, so i want to connect to my database (mysql) and choose the database i want to move. Afterwards, i would like to store ( the file/files i guess ) into my disk and be able to copy this database into another sql server.
My advice would be to do as little work as possible :-). Hence you should consider exporting your data using a tool which comes with MySQL: mysqldump. Don't export with the 'generate the SQL for create tables' option, since that will introduce MySQL-specific SQL.
How about writing a script that connects to both the old database and the new database and transfers, row by row, the contents of every table?
That way, among other things, you wouldn't have to worry about incompatibilities between your export tool and your import tool.
Colin
-- Colin W. Wetherbee http://hydrogen.denterprises.org/
That sounds great but unfortunately there are 3 sql server not connected each other, so i have to export the database and import the data to other 2 server ( using a disk or a Zip-drive.
