Database backups unusable with one insert per line

Just trying to restore a database backup and it is taking forever to run through Sequel Pro, and we realize there’s a separate insert for each database entry/row, which is terribly inefficient and ends up timing out in many cases. For example, trying to push up a 67MB backup via Sequel Pro, after more than 30 minutes only about 1 MB had been pushed up.

Other backup solutions – e.g. via phpMyAdmin or WP Migrate DB – use a single insert for multiple rows. These generally appear to function well, and import quickly.

Is this something that can be changed, or fixed, or is there a particular reason you built it this way?

If not we’re going to have to switch to a different backup solution.