Bug #45003 Allow mysqldump to save dump files per database
Submitted: 21 May 2009 8:44 Modified: 24 Sep 2009 8:57
Reporter: Mikiya Okuno Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: mysqldump Command-line Client Severity:S4 (Feature request)
Version: OS:Any
Assigned to: CPU Architecture:Any

[21 May 2009 8:44] Mikiya Okuno
While mysqldump has --result-file option, it stores all data into a huge single file. This is not an ideal operation for DBAs in the point of manageability point of view. If the command has --result-dir option and stores data into separate files per database or per table, it should be more useful.

How to repeat:

Suggested fix:
[24 Sep 2009 8:57] Susanne Ebrecht
Many thanks for writing a feature request.

Verified as described.
[11 Dec 2009 14:52] MySQL Verification Team
A patch for mysql 5.1

Attachment: bug45003.patch (application/octet-stream, text), 9.14 KiB.

[11 Dec 2009 14:57] MySQL Verification Team
Please review the patch. It works on my environment.

The patched mysqldump will:

- have --backup-basedir option. If specified, dump files are created under the directory per DB.
- create sub-directory under backup-basedir per backup if --backup-basedir option is specified. sub-directory has a name whose format is NNNNNN. Sub-directory name will be incremented each time when a sub-directory is created.
- will create database-name.sql files under the sub-directory if --backup-basedir option is specified.

Kind regards!
[14 Dec 2009 1:49] MySQL Verification Team
Fixed an error message.

Attachment: bug45003.patch (application/octet-stream, text), 9.15 KiB.

[18 Mar 2010 15:54] Qamar Sheikh
how do you implerment this fix ?
[15 Nov 2014 10:17] Daniƫl van Eeden
This is an RFE for file-per-database. There is also RFE Bug #6945 which requests file-per-table.