Any feedback on Big Dump? (no, I mean the SQL tool...)

You are viewing this site as a guest. Join our community to get your questions answered and share knowledge. Active members may advertise and ask for a website critique.

decibel.places posted this at 23:21 — 30th June 2008.

They have: 665 posts

Joined: Jun 2008

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.

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.sql

decibel.places posted this at 03:55 — 1st July 2008.

They have: 665 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.

Joined: Sep 2006

Ya, it will spike the server load for a while, but I've never had it crash from large imports.