Search Results
                    
                    
            https://dev.mysql.com/doc/refman/8.4/en/myisam-crash-recovery.html
                                 This section describes how to check for and deal with data corruption in MySQL databases. When performing crash recovery, it is important to understand that each MyISAM table tbl_name in a database corresponds to the three files in the database ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/myisampack.html
                                If you are not in the database directory, you should specify the path name to the file. (myisampack creates an intermediate file named tbl_name.TMD in the database directory while it compresses the table. When the table is used later, the server ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-installation.html
                                This section covers hardware and software requirements; networking issues; installation of NDB Cluster; basic configuration issues; starting, stopping, and restarting the cluster; loading of a sample database; and performing queries. We use the ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-limitations.html
                                You can report any discrepancies that you encounter to the MySQL bugs database using the instructions given in Section 1.6, “How to Report Bugs or Problems”.  In the sections that follow, we discuss known limitations in current releases of NDB ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-replication-backups.html
                                Create any databases on the replica cluster that are present on the source cluster and that are to be replicated. Important A CREATE DATABASE (or CREATE SCHEMA) statement corresponding to each database to be replicated must be executed on each SQL ... This section discusses making backups and restoring from them using NDB Cluster ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-replication-preparation.html
                                 Preparing the NDB Cluster for replication consists of the following steps: Check all MySQL servers for version compatibility (see Section 25.7.2, “General Requirements for NDB Cluster Replication”). To provide replication backup capability, you ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-single-user-mode.html
                                 Single user mode enables the database administrator to restrict access to the database system to a single API node, such as a MySQL server (SQL node) or an instance of ndb_restore. Once the cluster has entered single user mode, only the designated ...When entering single user mode, connections to all other API nodes are closed gracefully and all running transactions are ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/mysql-tzinfo-to-sql.html
                                 The mysql_tzinfo_to_sql program loads the time zone tables in the mysql database. It is used on systems that have a zoneinfo database (the set of files describing time zones). If your system does not have a zoneinfo database, you can use the ...One ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/optimization.html
                                Depending on your job role (developer, DBA, or a combination of both), you might optimize at the level of individual SQL statements, entire applications, a single database server, or multiple networked database servers. Optimizing CPU and memory ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/optimizing-innodb-transaction-management.html
                                The default MySQL setting AUTOCOMMIT=1 can impose performance limitations on a busy database server. InnoDB must flush the log to disk at each transaction commit if that transaction made modifications to the database. Killing the database process ...