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/optimizing-database-structure.html
In your role as a database designer, look for the most efficient way to organize your schemas, tables, and columns. As when tuning application code, you minimize I/O, keep related items together, and plan ahead so that performance stays high as the ...
https://dev.mysql.com/doc/refman/5.7/en/optimizing-myisam.html
The MyISAM storage engine performs best with read-mostly data or with low-concurrency operations, because table locks limit the ability to perform simultaneous updates. In MySQL, InnoDB is the default storage engine rather than MyISAM.
https://dev.mysql.com/doc/refman/5.7/en/optimizing-server.html
This section discusses optimization techniques for the database server, primarily dealing with system configuration rather than tuning SQL statements. The information in this section is appropriate for DBAs who want to ensure performance and ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-lock-tables.html
The Performance Schema exposes lock information through these tables: metadata_locks: Metadata locks held and requested table_handles: Table locks held and requested The following sections describe these tables in more detail.
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-miscellaneous-tables.html
The following sections describe tables that do not fall into the table categories discussed in the preceding sections: host_cache: Information from the internal host cache.
https://dev.mysql.com/doc/refman/5.7/en/programs-installation.html
The programs in this section are used when installing or upgrading MySQL.
https://dev.mysql.com/doc/refman/5.7/en/replication-features-charset.html
The following applies to replication between MySQL servers that use different character sets: If the source has databases with a character set different from the global character_set_server value, you should design your CREATE TABLE statements so ...
https://dev.mysql.com/doc/refman/5.7/en/replication-statements-replica.html
Section 13.4.1, “SQL Statements for Controlling Replication Source Servers”, discusses statements for managing source servers. In addition to the statements described here, SHOW SLAVE STATUS and SHOW RELAYLOG EVENTS are also used with replicas.
https://dev.mysql.com/doc/refman/5.7/en/resolve-stack-dump.html
Stack traces from official MySQL builds are always symbolized, so there is no need to use resolve_stack_dump. Invoke resolve_stack_dump like this: resolve_stack_dump [options] symbols_file [numeric_dump_file] The symbols file should include the ...
https://dev.mysql.com/doc/refman/5.7/en/resolveip.html
The resolveip utility resolves host names to IP addresses and vice versa.