Point-in-Time (Incremental) Recovery • --triggers : Dump triggers for tables 7.4.5.4 Dumping Table Definitions and Content Separately 7.4.5.5 Using mysqldump to Test for Upgrade Incompatibilities shell>  mysqldump --no-data test > dump-defs.sql shell>  mysqldump --no-create-info test > dump-data.sql shell>  mysqldump --no-data --routines --events test > dump-defs.sql The  --triggers  option is enabled by default so that when tables are dumped, they are accompanied by any triggers they have. The other options are disabled by default and must be specified explicitly to dump the corresponding objects. To disable any of these options explicitly, use its skip form:  --skip-events , --skip-routines , or  --skip-triggers . The  --no-data  option tells  mysqldump  not to dump table data, resulting in the dump file containing only statements to create the tables. Conversely, the  --no-create-info  option tells  mysqldump  to suppress CREATE  statements from the output, so that the dump file contains only table data. For example, to dump table definitions and data separately for the  test  database, use these commands: For a definition-only dump, add the  --routines  and  --events  options to also include stored routine and event definitions: When contemplating a MySQL upgrade, it is prudent to install the newer version separately from your current production version. Then you can dump the database and database object definitions from the production server and load them into the new server to verify that they are handled properly. (This is also useful for testing downgrades.) On the production server: On the upgraded server: Because the dump file does not contain table data, it can be processed quickly. This enables you to spot potential incompatibilities without waiting for lengthy data-loading operations. Look for warnings or errors while the dump file is being processed. After you have verified that the definitions are handled properly, dump the data and try to load it into the upgraded server. On the production server: On the upgraded server: Now check the table contents and run some test queries. Point-in-time recovery refers to recovery of data changes up to a given point in time. Typically, this type of recovery is performed after restoring a full backup that brings the server to its state as of the time the 7.5 Point-in-Time (Incremental) Recovery shell>  mysql < dump-data.sql shell>  mysqldump --all-databases --no-create-info > dump-data.sql shell>  mysql < dump-defs.sql shell>  mysqldump --all-databases --no-data --routines --events > dump-defs.sql