MySQL Server | Part 3
MySQL Server – MERGE
MERGE offers the possibility of multiple tables of type MyISAM with the same structure to combine in one table and the requests to execute.
MEMORY (HEAP)
Usage: Management of temporary tables. The definition of the tables is permanently stored on disk. The data is stored in memory. There are, however, does not support all data types. At a restart of the server, the table structures are still present; the content must be read again, for example, from permanent tables. There are special procedures implemented for memory management to reuse the space from deleted records during the next insertion.
EXAMPLE
Usage: Code example for the development of its own storage engine. EXAMPLE has functions for creating a table that functions for writing and reading of the records only hinted at. A SELECT statement always returns an empty result set.
BDB
BDB is an acronym for Berkeley DataBase. This storage engine was developed by Sleepycat Software and later sold to Oracle. The BDB provides transaction security, and special arrangements so as to maintain a system failure, the stored data.
The InnoDB storage engine as of version 5.1.12 no longer continues to be supported.
FEDERATED
The FEDERATED engine provides access to tables located on a different server. When you create a FEDERATED table type, then the remote table must exist on the other server already. The local server acts as a client that accesses the remote server. The FEDERATED engine behaves as a federated information system, which means that it does not store the data itself, but provides access to the remote server while this can be also accessed the data. In the version 5.0 can only be accessed by other MySQL server. It is planned to extend this engine that are accessible to other DBMS.
ARCHIVE
The ARCHIVE storage engine is designed for storing large amounts of data at a possible economic use of the space available. It can no indexes are created. Only the requests INSERT and SELECT are supported. The fast access to data is not in the foreground.
Before saving the data on the storage, they are first collected in a compression buffer. When a series of insert operations is complete, the optimal compression algorithm is determined and the data is compressed output.
If during a sequence of ‘insert operations’ by another user is a SELECT query, an early edition of the compression and the compression data buffer is enforced.
CSV
In the CSV engine, the data are stored in CSV format, i.e., Numbers are not binary, but saved as individual digits, and the individual values are separated by commas.
BLACKHOLE
BLACKHOLE was developed to check the syntax of SQL statements and write a binary log. The data is not saved. This allows syntax checks SQL statements are executed without the space provided to store the data needs. The output of the binary log can be enabled and disabled via a parameter.
The BLACKHOLE engine is ideal for the following tasks:
- Syntax check of dump files
- Test data replication by subsequent comparison of the binary logs on the master server and slave servers.
- Time measurements to determine the effort for writing the binary logs.
NDB
NDB is an acronym for Network Data Base. The NDB Storage Engine is a stand-alone component that persistent storage made possible by information and responsible for coordinating all requests for data nodes into a MySQL Cluster. Applications directly to the NDB Storage Engine about NDB API or access a MySQL nodes. Accessing MySQL on a node is for application programmers to design much easier, as they can be used in this case, standard SQL commands and learning the NDB specialties is not necessary.
The NDB API is a multithread-enabled interface to accept all incoming data requests. For each request starts one or more threads. On the NDB API only a sequential access is possible, whereby the performance of the cluster in very many incoming requests is probably limited.
Falcon
The Falcon storage engine has been developed by MySQL AB. You should comply with the MySQL version 6.0 more than transactional storage engine. Some functions such as foreign key, however, should be included only in version 6.1. On 13 April 2010 were known to Oracle, that the development of the Falcon engine is set .
Engines from other providers
Besides the official Engines offer more than one manufacturer, other engines with other properties re available with same or additional functions.
Revision Engine
An important function of a database, it is to be able versioned data, guaranteed addition to the pure data storage, that data will be restored as they were at a particular time. This is necessary to meet legal requirements, but can also save the progress of product characteristics. The revision of DDEngine engine adds an automatic versioning added as a plug at the level of a storage engine. To store the data physically the supplied storage engines can be used.
DB2 on i5/OS
In April 2007, the availability of MySQL on the IBM System i5 (formerly iSeries or AS/400 announced). integrated into the operating system DB2 database was to function as a database engine for MySQL. These implicit transactions are supported. IBM hopes to gain new areas of application of the system i5 for MySQL and PHP applications open.
Bright House Engine
Company Info Bright [provides 16] in Toronto, the Bright House engine. It is designed for data warehouse applications designed and aligned so for processing large amounts of data. Indices are not supported. The data is compressed, stored, this according to the manufacturer 90% of the space can be saved.
NitroEDB
The firm NitroSecurity in Portsmouth (USA) presents the NitroEDB engine. It was developed for the real-time monitoring of networks.
MySQL Administration
To manage MySQL databases included command-line client (MySQL and MySQLAdmin commands are used). As a graphical management console, MySQL AB MySQL Administrator and MySQL Query Browser is used in the visualization.
One of many alternatives phpMyAdmin is written in the scripting language PHP open-source application. The graphical user interface can be operated via a browser. You can use it to manage MySQL databases. phpMyAdmin is mainly used to manage MySQL databases used on Web servers on which the individual customers have no rights to run MySQL and MySQLAdmin directly.
To create and manage backups of the databases on Web servers are – if there are no rights for the execution of MySQLDump – which also often used in PHP open-source applications or phpMyBackupPro and MySQLDumper. For an uninterrupted system, offers the Master / slave replication, the backup will be performed on the slave.
Study: From Wikipedia, the free encyclopedia. The text is available under the Creative Commons.
