I'm curious if anyone has any real-world benchmark results, or even solid speculation as to what might be faster to backup a 70 Gigabyte database: SQLYog's Backup option or just plain old mysqldump?
Assume both would be running on a remote desktop on the LAN and pulling all the data across the network to the local hard-drive.
If for some reason SQLYog is faster in that case, what about versus mysqldump ran locally on the server? (Is SQLYog still faster)?
Obviously with that much data, we've had it take as long as a few days to export to a .sql file via mysqldump.
We've never tried using SQLYog for such a dump.
And as an aside “feature/nice to have”, I notice after I do a SQL backup, the “History” tab doesn't show a SQL statement to re-create the dump. Much like you have the INSERT, ALTER, SELECT, etc. It would be helpful if there was a
“mysqldump –opts –lock –tables foo,bar,bee > filename.sql”
in the list of history statements. I realize of course, you aren't actually USING mysqldump, but your options are effectively a one:one match and therefore would translate accordingly. Then if/when I need to re-create the same dump locally on the server without the aide of SQLYog, I can do so. Just a thought.
Running 8.12 Enterprise if that matters.
