Any feedback on Big Dump? (no, I mean the SQL tool...)
Having copied a healthy sized MySQL database twice in the past few months, it's not fun doing it in 20 separate export and import steps
Has anybody used Big Dump?
Having copied a healthy sized MySQL database twice in the past few months, it's not fun doing it in 20 separate export and import steps
Has anybody used Big Dump?
pr0gr4mm3r posted this at 02:28 — 1st July 2008.
He has: 1,502 posts
Joined: Sep 2006
For large imports, why not just copy the SQL file to the server and import it from the command line?
mysql --user=username --pass=password --host=dbserver database < /path/file.sqldecibel.places posted this at 03:55 — 1st July 2008.
He has: 1,494 posts
Joined: Jun 2008
Big Dump segments the imports for you, to not hog too much SQL bandwidth or cause timeouts.
They do in fact recommend dumping the db from the command line
This db has about 200MB of SQL text. I found the SQL server choked on imports larger than about 15MB
pr0gr4mm3r posted this at 18:34 — 1st July 2008.
He has: 1,502 posts
Joined: Sep 2006
Ya, it will spike the server load for a while, but I've never had it crash from large imports.
Want to join the discussion? Create an account or log in if you already have one. Joining is fast, free and painless! We’ll even whisk you back here when you’ve finished.