vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello, I have a snapshot of a database which I migrated about a week ago to do a proof of concept. Now that it has been proven out, I need to migrate the database which has the most current data AND the snapshot which I took. I have dumped out the database using the typical "mysqldump -h localhost dbname > dbname.sql", but when I restore the dbname.sql file, do I use the "mysql -h localhost dbname < dbname.sql" command, or are there additional flags/options which need to be included? Thanks in advance, Sheel Shah |
| ||||
| <sheel331@yahoo.com> wrote in message news:3d645531-3e1e-4c8a-9575-4fa57e732a9f@34g2000hsf.googlegroups.com... > Hello, > > I have a snapshot of a database which I migrated about a week ago to > do a proof of concept. Now that it has been proven out, I need to > migrate the database which has the most current data AND the snapshot > which I took. > > I have dumped out the database using the typical "mysqldump -h > localhost dbname > dbname.sql", but when I restore the dbname.sql > file, do I use the "mysql -h localhost dbname < dbname.sql" command, > or are there additional flags/options which need to be included? > > Thanks in advance, > Sheel Shah Now that your proof of concept has been accepted, apply the same changes to your production database as you did to the snapshot (after you back it up, of course). Trying to stuff data from a mismatched database is asking for trouble. |