The Output File Options section controls
the formatting of the backup file. At present there is only one
Backup Type
available, the SQL
Files
format, which outputs a file similar to the
output of the mysqldump
utility.
No CREATEs will suppress CREATE
DATABASE
statements. This can be useful if you need to
restore the data to a different database than it was backed up
from.
No EXTENDED INSERTS will suppress the
default behavior of combining multiple inserts into a single
statement (for example INSERT INTO test VALUES
('1',Some data',2234),('2','Some More Data',23444)
).
While the EXTENDED INSERT
syntax is more
efficient both in terms of storage and execution, it is not
compatible with most RDBMSes.
Add DROP Statements adds DROP
TABLE IF EXISTS
statements to the backup file.
If your backup project includes views then you must choose this option. Restoration of a view is a two step process that involves creating a dummy table with the same name as the view. This table must be dropped before the view can be recreated.
Complete INSERTs will produce full
INSERT
statements that include a column list
(for example, INSERT INTO tablename(columnA, columnB)
VALUES(valueA, valueB)
). Without this option the
column list will be omitted.
Comment writes additional backup information to the backup file in the form of SQL comments.
Fully Qualified Identifiers causes
MySQL Administrator to write statements in the format,
schema_name.table_name
, instead of writing
only the object name. If you enable fully qualified identifiers
you will not be able to restore your backup to a different
schema. Selecting this option will also display a warning dialog
requesting acknowledgement of this.
Under Linux this check box is labeled Don't write full path. In this case you need to check this box if you later want to restore to another database schema.
Compatibility mode creates backup files that are compatible with older versions of MySQL Administrator.
ANSI Quotes will cause all table and database names to be quoted with ANSI style double quotes instead of backticks.
Disable keys will add an ALTER
TABLE ... DISABLE KEYS
statement to the backup file
before the INSERT
statements that populate
the tables. This allows for faster recovery by loading all data
before rebuilding the index information.