Created
June 24, 2015 08:32
-
-
Save rakauchuk/45df853f6a4e9ef5172b to your computer and use it in GitHub Desktop.
Dumping MySQL Stored Procedures, Functions and Triggers
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MySQL 5 has introduced some new interesting features, like stored procedures and triggers. I will show in this small post how we can backup and restore these components using mysqldump. | |
mysqldump will backup by default all the triggers but NOT the stored procedures/functions. There are 2 mysqldump parameters that control this behavior: | |
—routines – FALSE by default | |
—triggers – TRUE by default | |
This means that if you want to include in an existing backup script also the triggers and stored procedures you only need to add the —routines command line parameter: | |
$ mysqldump <other mysqldump options> --routines outputfile.sql | |
Let’s assume we want to backup ONLY the stored procedures and triggers and not the mysql tables and data (this can be useful to import these in another db/server that has already the data but not the stored procedures and/or triggers), then we should run something like: | |
$ mysqldump --routines --no-create-info --no-data --no-create-db --skip-opt <database> > outputfile.sql | |
and this will save only the procedures/functions/triggers of the . If you need to import them to another db/server you will have to run something like: | |
$ mysql <database> < outputfile.sql |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment