PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 296.6Kb
Man Pages (Zip)
- 402.0Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/multiple-windows-servers.html
The following sections describe how to start each server with different values for those options that must be unique per server, such as the data directory. You can run multiple servers on Windows by starting them manually from the command line, ...
https://dev.mysql.com/doc/refman/8.0/en/multiple-windows-services.html
To set up multiple MySQL services, you must make sure that each instance uses a different service name in addition to the other parameters that must be unique per instance. On Windows, a MySQL server can run as a Windows service. The procedures for ...
https://dev.mysql.com/doc/refman/8.0/en/myisam-repair.html
The discussion in this section describes how to use myisamchk on MyISAM tables (extensions .MYI and .MYD). You can also use the CHECK TABLE and REPAIR TABLE statements to check and repair MyISAM tables. See Section 15.7.3.2, “CHECK TABLE ...
https://dev.mysql.com/doc/refman/8.0/en/myisam-storage-engine.html
MyISAM is based on the older (and no longer available) ISAM storage engine but has many useful extensions. Table 18.2 MyISAM Storage Engine Features Feature Support B-tree indexes Yes Backup/point-in-time recovery (Implemented in the server, rather ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-backup-concepts.html
In the listing just shown, backup_id stands for the backup identifier and node_id is the unique identifier for the node creating the file. A backup is a snapshot of the database at a given time. The data actually stored in the database tables at ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-computer-definition.html
(NDB 8.0.13) This is a unique identifier, used to refer to the host computer elsewhere in the configuration file. The [computer] section has no real significance other than serving as a way to avoid the need of defining host names for each node in ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-disk-data-objects.html
This means that each Disk Data object must be uniquely named (and not merely each Disk Data object of a given type). NDB Cluster Disk Data storage is implemented using the following objects: Tablespace: Acts as containers for other Disk Data ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-limitations-unsupported.html
A number of features supported by other storage engines are not supported for NDB tables. Trying to use any of these features in NDB Cluster does not cause errors in or of itself; however, errors may occur in applications that expects the features ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-logs-cluster-log.html
ticket_id is a unique identifier handed out by the arbitrator when it is selected to all the nodes that participated in its selection; this is used to ensure that each node requesting arbitration was one of the nodes that took part in the selection ... The following table lists the most common NDB cluster log ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndb-innodb-workloads.html
NDB Cluster has a range of unique attributes that make it ideal to serve applications requiring high availability, fast failover, high throughput, and low latency. Due to its distributed architecture and multi-node implementation, NDB Cluster also ...