©SQL :: Manager
HomeProgram InformationTechnical detailsFree downloadDonate for a cup of coffee
myway SQL Manager for MySQL and MariaDB, Download on Uptodown
MySQL, MariaDB display Server Engines

Display of the MySQL and MariaDB server engines

Server engines This module a part of the host administration
MySQL Server engines

Displays the installed server engines with their properties.

In addition, status or mutex of an engine can be shown.

MySQL and MariaDB share many of the same server engines, but there are some differences between them . The engine choice depends on the specific needs of the application, such as performance, scalability, data persistence, and transaction support.

Engines supported by both MySQL and MariaDB:

InnoDB: InnoDB is the default and most commonly used storage engine for MySQL and MariaDB. It offers ACID-compliant transactions, row-level locking, and crash recovery.

MyISAM: MyISAM is an older storage engine still supported by MySQL and MariaDB. However, it is not recommended for use in production environments because it does not support transactions and row-level locking.

Memory: The memory engine stores data in memory, making it very fast for reads and writes. However, it is not permanent and all data will be lost when the server is restarted.

NDB: The NDB storage engine, also called MySQL Cluster, offers high availability and scalability, but has some limitations, such as a maximum Line size of 8 KB.

CSV: The CSV engine stores data in comma-separated value files, making it easy to import and export data to and from other applications. However, it does not support indexes or transactions.

Archive: The Archive engine is optimized for storing large amounts of data that is rarely accessed. The engine compresses data on the hard drive, making it very space-efficient.

Blackhole: The Blackhole engine is used for data replication. It discards all writes, but can be used to redirect read requests to another server.

Federated: The Federated engine allows data to be stored on a remote MySQL or MariaDB server and access from a local server as if it were local data.

Merge: The merge engine allows multiple tables to be combined into a single virtual table. This can be useful for querying data from multiple sources with a single query.

In addition, MariaDB has some engines that are not supported by MySQL:

Aria: The Aria storage engine is a crash-proof alternative to the MyISAM engine with support for transactions and row-level locking.

XtraDB: XtraDB is a high-performance fork of InnoDB with additional features such as improved scalability and better handling of write-intensive workloads.

TokuDB: The TokuDB engine is designed for high-performance, high-compression workloads and supports fast inserts, updates, and deletes on large datasets.

MySQL engines are selected when creating tables
Updated: 2023-09-14ImprintContactTerms & conditionsPrivacy & CookiesUpdatesSitemapFacebookLinkedinTwitterStatistics©2020-2024 Heino Cunze-Fischer