I guess I should have quantified my recommendation by asking how big the original database was. Running MySQL dump and re-import on a 25GB database can take a significant amount of time that may prove unacceptable based on your traffic levels. In our environments where the MySQL versions are the same or within a few minor revisions and the physical platforms are the same, moving the binary file provides a more rapid transition option.
However, if your database is of more modest size, MySQL dump can provide a nice method to transfer data. You can even chain the dump and import process together to move the bottle neck from disk to the network and cause the transfer to complete faster. Here's an untested example: [EMAIL PROTECTED] ~]$ mysqldump -u USER -pPASSWORD DATABASE_NAME | \ mysql -h newserver.com -u USER -pPASSWORD DATABASE_NAME Please note, this will dump your SQL data over the unencrypted MySQL protocol, so you may want to look at creating a SSH tunnel between your two hosts for added security. The point to copy the appropriate sections from your my.cnf is also a good one. If you have more information on the specifics of your old and new environment, this group can probably be even more helpful. - Jesse Alex Malinovich wrote: > I definitely agree with Hassan. Moving the MySQL binaries over is > definitely easy to do, but if the versions of MySQL don't match > precisely you could be asking for trouble. The safe option is to just > use mysqldump to create a backup and then import it on the new db. -- Jesse Proudman Blue Box Group, LLC p. 800-613-4305 x 801 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
