MySQL :: MySQL 5.7 Reference Manual

Search Results

Displaying 441 to 450 of 1125 total results

26.4.3.52 The waits_global_by_latency and x$waits_global_by_latency Views

https://dev.mysql.com/doc/refman/5.7/en/sys-waits-global-by-latency.html

The waits_global_by_latency and x$waits_global_by_latency views have these columns: events The event name. total_latency The total wait time of timed occurrences of the event. avg_latency The average wait time per timed occurrence of the event.

6.2.18 SQL-Based Account Activity Auditing

https://dev.mysql.com/doc/refman/5.7/en/account-activity-auditing.html

Applications can use the following guidelines to perform SQL-based auditing that ties database activity to MySQL accounts. When a client connects successfully, the server authenticates the client to a particular row in this table. The User and Host ...

15.5 The ARCHIVE Storage Engine

https://dev.mysql.com/doc/refman/5.7/en/archive-storage-engine.html

The ARCHIVE storage engine produces special-purpose tables that store large amounts of unindexed data in a very small footprint. To enable this storage engine if you build MySQL from source, invoke CMake with the -DWITH_ARCHIVE_STORAGE_ENGINE ...

6.4.5.3 MySQL Enterprise Audit Security Considerations

https://dev.mysql.com/doc/refman/5.7/en/audit-log-security.html

By default, contents of audit log files produced by the audit log plugin are not encrypted and may contain sensitive information, such as the text of SQL statements. For security reasons, audit log files should be written to a directory accessible ...

6.4.5 MySQL Enterprise Audit

https://dev.mysql.com/doc/refman/5.7/en/audit-log.html

Note MySQL Enterprise Audit is an extension included in MySQL Enterprise Edition, a commercial product. MySQL Enterprise Edition includes MySQL Enterprise Audit, implemented using a server plugin named audit_log. MySQL Enterprise Audit uses the ...

15.6 The BLACKHOLE Storage Engine

https://dev.mysql.com/doc/refman/5.7/en/blackhole-storage-engine.html

The BLACKHOLE storage engine acts as a “black hole” that accepts data but throws it away and does not store it. To examine the source for the BLACKHOLE engine, look in the sql directory of a MySQL source distribution. When you create a ...

13.7.6.2 CACHE INDEX Statement

https://dev.mysql.com/doc/refman/5.7/en/cache-index.html

| tbl_name PARTITION (partition_list) } IN key_cache_name tbl_index_list: tbl_name [{INDEX|KEY} (index_name[, index_name] ...)] partition_list: { partition_name[, partition_name] ... | ALL } The CACHE INDEX statement assigns table indexes to a ...

16.2.2.3 Startup Options and Replication Channels

https://dev.mysql.com/doc/refman/5.7/en/channels-startup-options.html

This section describes startup options which are impacted by the addition of replication channels. The following startup settings must be configured correctly to use multi-source replication. If this variable is set to FILE, attempting to add more ...

11.3.2 The CHAR and VARCHAR Types

https://dev.mysql.com/doc/refman/5.7/en/char.html

The CHAR and VARCHAR types are similar, but differ in the way they are stored and retrieved. They also differ in maximum length and in whether trailing spaces are retained. The CHAR and VARCHAR types are declared with a length that indicates the ...

10.5 Configuring Application Character Set and Collation

https://dev.mysql.com/doc/refman/5.7/en/charset-applications.html

For applications that store data using the default MySQL character set and collation (latin1, latin1_swedish_ci), no special configuration should be needed. If applications require data storage using a different character set or collation, you can ...

Displaying 441 to 450 of 1125 total results