On Feb 12, 2011 3:42 PM, "Raju s" <[email protected]> wrote: > > mysqldump -a *dbname *-u *user *-p*password* | ssh > *user*@*xxx.xxx.xxx.xxx*mysql -u > *user* -p*password* *dbname* >
If the SSH session drops in-between, you will be left with a mess on your hands! While bulk updating a production DB, it's good practice to do things in small and verifyable steps. Each step should also be minimized to ensure that it will not fail, and if it does fail it should be quick and easy to revert. Best option is to dump to a file, verify records, scp/rsync, and import into the other DB. Depending on the number of records, indexes may need to be temporarily disabled so the data is imported faster. - Raja _______________________________________________ ILUGC Mailing List: http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
