Dumping MySQL Stored Procedures, Functions and Triggers
MySQL 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.
What is Stored Procedure ?
A stored procedure, by definition, is a segment of declarative SQL code which is stored in the database catalog and can be invoked later by a program, a trigger or even a stored procedure.
What is Triggers ?
Triggers are event-driven specialized procedures, they are stored in and managed by the database. A trigger is a SQL procedure that initiates an action on an event ( Like: INSERT, DELETE or UPDATE) occurs.
When we simply execute mysqldump, It automatically takes backup of triggers but it will not backup stored procedures by default.
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 |
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:
1 | |
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:
1 | |
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:
1 | |
