The slave relay logs should be deleted; then execute START SLAVE;

The relay logs from the master should be used to replace the corrupted relay logs.

The slave relay logs should be deleted; execute CHANGE MASTER to adjust the replication relay log file name, then issue start SLAVE;

The slave needs to be restored from backup.

It reconfigures InnoDB Cluster if the cluster was stopped.

It performs InnoDB Cluster instances rolling restart.

It only starts all InnoDB Cluster instances.

It is not mandatory that all instances are running and reachable before running the command.

It stops and restarts all InnoDB Cluster instances and initializes the metadata.

It only stops and restarts all InnoDB Cluster instances.

It picks the minimum number of instances necessary to rebuild the quorum and reconfigures InnoDB Cluster.

They are converted to a highly compressible binary format.

The data format is identical to how MySQL stores the data on disk.

They are required to obtain FIPS security compliance.

The resulting files are easily human readable.

They are faster than logical backups because the process is a simple file or file system copy.

The redo logs are backed up first, then the transaction and archive tables.

The redo logs are backed up only if there are changes showing for the transactions tables.

The redo logs are not backed up at all.

The archive tables are backed up first, then the transaction tables and redo logs.

The transaction tables are backed up first, then the archive tables and redo logs.

Take a physical backup of the MySQL system.

Use the Clone Plugin to copy the data to another MySQL system.

Take a logical backup of the MySQL system.

Take your backup from a slave of the MySQL system.

installing and configuring the Connection Control plugin

avoiding concatenation of SQL statements and user-supplied values in an application

using stored procedures for any database access

using PREPARED STATEMENTS

Sort the “Exec" column and check for SQL queries with low Query Response Time index (QRTi) values.

Look for queries with low total latency times in the Latency section in the times series graph.

Look for queries with big prolonged spikes in row activity/access graph in the times series graph.

Sort the “Exec" column and check for SQL queries with high Query Response Time index (QRTi) values.

Use the AES_ENCRYPT() MySQL function on the option file.

Use mysql_secure_installation to encrypt stored login credentials.

Use a text editor to create a new defaults file and encrypt it from Linux prompt.

Use mysql_config_editor to create an encrypted file.

performance metrics

table definitions

access control lists

view definitions

server runtime configuration

server configuration rollback

stored procedure definitions

Set validate-user-plugins=caching_sha2_password in the configuration file.

Define CREATE USER ''@'%' IDENTIFIED WITH sha256_password in the MySQL instance.

Add default_authentication_plugin=mysql_native_password in the configuration file.

Add default_authentication_plugin=sha256_password in the configuration file.

general query log

audit log

slow query log

binary log

error log

It defines all innodb tablespace options relative to a starting parent directory.

It is not necessary because innodb_data_home_dir is already defined.

It allows scanning of other locations to discover more innodb tablespaces.

It moves all innodb tablespaces to the /innodb_extras directory to enable a new

innodb_data_home_dir to be defined.

It adds more temporary workspace in addition to the innodb_tmpdir location.

You can scale writes by creating a replicated mesh.

It guarantees near real-time replication between a master and a slave.

You can scale reads by adding multiple slaves.

MySQL Enterprise Backup will automatically back up from an available slave.

It allows backup to be done on the slave without impacting the master.

MySQL Replication monitoring

network-related information and network characteristics

MySQL Query Analysis data

CPU utilization

security-related advisor warnings

operating system memory utilization

disk usage and disk characteristics including disk advisors warnings

The Query Analyzer graph view range selector can extend to cover the same hour over multiple days.

It is possible to filter a Query Analyzer view graph by database and by table.

The Query Analyzer can plot a CPU utilization graph for remote hosts with a MySQL Enterprise Service Manager's built-in Agent installation.

It is possible to export statements included in a graph selection in CSV format.

mysqlpump --include-tables=db.% --result-file=all_db_backup.sql

mysqlpump > all_db_backup.sql

mysqlpump --include-databases=db --result-file=all_db_backup.sql

mysqlpump --include-databases=db% --result-file=all_db_backup.sql

information_schema

world

employee

sys

mysql

Updating index statistics is an I/O expensive operation.

Index statistics are calculated from pages buffered in the buffer pool for tables with InnoDB storage engine.

Setting innodb_stats_auto_recalc=ON causes statistics to be updated automatically when a new index is created.

Execution plans based on transient index statistics improve precision when innodb_stats_persistent_sample_pages is increased.

Increasing innodb_stats_persistent_sample_pages determines higher pages scanning speed, at the cost of increased memory usage.