Search Results
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-ndb-api-statistics.html
This reflects the creation of the hidden primary key that is a feature of all tables using the NDB storage engine. A number of types of statistical counters relating to actions performed by or affecting Ndb objects are available. Such actions ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-online-add-node-remarks.html
However, all data and indexes added to tables created after a new node group has been added are distributed automatically among all cluster data nodes, including those added as part of the new node group. Normal DML operations using NDB Cluster data ... This section provides general information about the behavior of and current limitations in adding NDB Cluster nodes ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-programs-ndb-blob-tool.html
This tool can be used to check for and remove orphaned BLOB column parts from NDB tables, as well as to generate a file listing any orphaned parts. It is sometimes useful in diagnosing and repairing corrupted or damaged NDB tables containing BLOB ...
https://dev.mysql.com/doc/refman/8.4/en/mysqldump-copying-to-other-server.html
On Server 2: $> mysql < dump.sql Use of --databases with the mysqldump command line causes the dump file to include CREATE DATABASE and USE statements that create the database if it does exist and make it the default database for the reloaded data.
https://dev.mysql.com/doc/refman/8.4/en/mysqldump-definition-data-dumps.html
The --no-data option tells mysqldump not to dump table data, resulting in the dump file containing only statements to create the tables. Conversely, the --no-create-info option tells mysqldump to suppress CREATE statements from the output, so that ...
https://dev.mysql.com/doc/refman/8.4/en/nontransactional-tables.html
This can happen if you try to create a table using a transactional storage engine that is not supported by your mysqld server (or that was disabled with a startup option). If mysqld does not support a storage engine, it instead creates the table as ... If you receive the following message when trying to perform a ROLLBACK, it means that one or more of the tables you used in the transaction do not support transactions: Warning: Some non-transactional changed tables couldn't be rolled back These nontransactional tables are not affected by the ROLLBACK ...
https://dev.mysql.com/doc/refman/8.4/en/optimizing-innodb-queries.html
To tune queries for InnoDB tables, create an appropriate set of indexes on each table. Do not create a separate secondary index for each column, because each query can only make use of one index. If you have many queries for the same table, testing ...Follow these guidelines for InnoDB indexes: Because each InnoDB table has a primary key (whether you request one or not), specify a set of primary key columns for each table, columns that are used in the most important and time-critical ...
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-stage-tables.html
The Performance Schema instruments stages, which are steps during the statement-execution process, such as parsing a statement, opening a table, or performing a filesort operation. Stages correspond to the thread states displayed by SHOW ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-triggers.html
If an upgraded replication source server still has old replicas using MySQL versions that do not support multiple triggers, an error occurs on those replicas if a trigger is created on the source for a table that already has a trigger with the same ... With statement-based replication, triggers executed on the source also execute on the ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-failover.html
There are several variants of this method, the difference being in the manner in which data dumps and transactions from binary logs are transferred to the replica, as outlined here: Data Set Create a dump file using mysqldump on the source server.