mysqldump — A Database Backup Program This option suppresses all  CREATE LOGFILE GROUP  and  CREATE TABLESPACE  statements in the output of  mysqldump . Write  REPLACE  statements rather than  INSERT  statements. The following options print debugging information, encode debugging information in the dump file, or let the dump operation proceed regardless of potential problems. Permit creation of column names that are keywords. This works by prefixing each column name with the table name. Write additional information in the dump file such as program version, server version, and host. This option is enabled by default. To suppress this additional information, use  --skip-comments . Write a debugging log. A typical  debug_options  string is  d:t:o, file_name . The default value is d:t:o,/tmp/mysqldump.trace . This option is available only if MySQL was built using  WITH_DEBUG . MySQL release binaries provided by Oracle are  not  built using this option. Print some debugging information when the program exits. This option is available only if MySQL was built using  WITH_DEBUG . MySQL release binaries provided by Oracle are  not  built using this option. Print debugging information and memory and CPU usage statistics when the program exits. This option is available only if MySQL was built using  WITH_DEBUG . MySQL release binaries provided by Oracle are  not  built using this option. If the  --comments  option is given,  mysqldump  produces a comment at the end of the dump of the following form: However, the date causes dump files taken at different times to appear to be different, even if the data are otherwise identical.  --dump-date  and  --skip-dump-date  control whether the date is added to the comment. The default is  --dump-date  (include the date in the comment).  --skip-dump-date suppresses date printing. 487 • --force ,  -f • --dump-date • --debug-info • --debug-check • --debug[= debug_options ] ,  -# [ debug_options ] • --comments ,  -i • --allow-keywords • --replace Debug Options -- Dump completed on  DATE