PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.2Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/windows-server-first-start.html
This section gives a general overview of starting the MySQL server. The following sections provide more specific information for starting the MySQL server from the command line or as a Windows service. The information here applies primarily if you ...
https://dev.mysql.com/doc/refman/5.7/en/create-index.html
This guideline is especially important for InnoDB tables, where the primary key determines the physical layout of rows in the data file. When the innodb_stats_persistent setting is enabled, run the ANALYZE TABLE statement for an InnoDB table after ... CREATE [UNIQUE | FULLTEXT | SPATIAL] INDEX index_name [index_type] ON tbl_name (key_part,...) [index_option] [algorithm_option | lock_option] ...
https://dev.mysql.com/doc/refman/5.7/en/faqs-storage-engines.html
Is there an advantage to using the InnoDB storage engine exclusively, as opposed to a combination of InnoDB and non-InnoDB storage engines? A.2.6. That chapter contains information about all MySQL storage engines except for the InnoDB storage engine ...Where can I obtain complete documentation for MySQL storage engines? ...
https://dev.mysql.com/doc/refman/5.7/en/partitioning-limitations.html
For partitioned tables using the MyISAM storage engine, increasing myisam_max_sort_file_size may improve performance; partitioning and repartitioning operations involving InnoDB tables may be made more efficient by enabling innodb_file_per_table.
https://dev.mysql.com/doc/refman/5.7/en/binary-log.html
Within an uncommitted transaction, all updates (UPDATE, DELETE, or INSERT) that change transactional tables such as InnoDB tables are cached until a COMMIT statement is received by the server. For example, if you are using InnoDB tables and the ...
https://dev.mysql.com/doc/refman/5.7/en/flush.html
Note The descriptions here that indicate tables are flushed by closing them apply differently for InnoDB, which flushes table contents to disk but leaves them open. InnoDB supports FOR EXPORT for tables that have their own .ibd file file (that is, ...| table_synonym WITH READ LOCK | table_synonym tbl_name [, tbl_name] ...
https://dev.mysql.com/doc/refman/5.7/en/keyring-plugin-installation.html
For example, the InnoDB storage engine uses the keyring for tablespace encryption, so the keyring plugin must be loaded and available prior to InnoDB initialization. InnoDB tablespace encryption requires that the keyring plugin to be used be loaded ... Keyring service consumers require that a keyring plugin be ...
https://dev.mysql.com/doc/refman/5.7/en/downgrading-to-previous-series.html
System Table Changes InnoDB Changes Logging Changes SQL Changes System Table Changes In MySQL 5.7.13, system table columns that store user@host string values were increased in length. InnoDB Changes As of MySQL 5.7.5, the FIL_PAGE_FLUSH_LSN field, ... Before downgrading from MySQL 5.7, review the information in this ...
https://dev.mysql.com/doc/refman/5.7/en/drop-tablespace.html
It is supported with all MySQL NDB Cluster 7.5 releases, and with InnoDB in the standard MySQL Server as well. For an InnoDB tablespace, all tables must be dropped from the tablespace prior to a DROP TABLESPACE operation. As with the InnoDB system ... DROP TABLESPACE tablespace_name [ENGINE [=] engine_name] This statement drops a tablespace that was previously created using CREATE ...
https://dev.mysql.com/doc/refman/5.7/en/mysqldump.html
(Available as part of the Enterprise subscription.) It provides the best performance for InnoDB backups with minimal disruption; it can also back up tables from MyISAM and other storage engines; and it provides a number of convenient options to ...