A configurable MySQL database dumping tool for creating partial dumps, masking sensitive data, and handling large datasets.
slimdump is a command-line tool for creating configurable dumps of large MySQL databases. It solves the problem of exporting only relevant parts of production databases while masking or replacing sensitive data like personal information. Unlike generic dump tools, it uses XML configuration files to define exactly what to export, making dumps reproducible and secure.
Developers and DevOps engineers working with MySQL databases who need to create partial, anonymized, or reproducible dumps for debugging, testing, or data analysis without exposing sensitive information.
Developers choose slimdump for its fine-grained control over database exports via configuration files, built-in data masking for GDPR compliance, and ability to handle large datasets efficiently. It fills the gap between mysqldump's limited configurability and manual scripting, offering a shareable, automated solution for secure data extraction.
A tool for creating configurable dumps of large MySQL-databases.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Allows precise definition of dump modes per table and column, including schema-only, full data, and BLOB omission, via XML configs, as shown in the wildcard and conditional examples.
Supports masking sensitive data and using Faker for realistic dummy data, facilitating GDPR-compliant exports without manual scripting, detailed in the replacement configuration section.
XML configuration files can be version-controlled and shared across teams, ensuring consistent dump processes, which is a core philosophy highlighted in the README.
Currently only supports MySQL, as explicitly stated in the README, making it unsuitable for projects with multi-database architectures or those migrating away from MySQL.
CSV output mode is marked as experimental with potential breaking changes in output formatting, which could disrupt workflows relying on this feature for data processing.
Requires PHP and Composer for installation, which may not align with tech stacks that avoid PHP or prefer standalone binary tools, despite mentions of a future .phar package.