Language Selection

English French German Italian Portuguese Spanish

MySQL Storage Engines

Filed under
Software

Data in MySQL is stored in files (or memory) using a variety of different techniques. Each of these techniques employ different storage mechanisms, indexing facilities, locking levels and ultimately provide a range of different functions and capabilities. By choosing a different technique you can gain additional speed or functionality benefits that will improve the overall functionality of your application.

For example, if you work with a large amount of temporary data, you may want to make use of the MEMORY storage engine, which stores all of the table data in memory. Alternatively, you may want a database that supports transactions (to ensure data resilience).

Each of these different techniques and suites of functionality within the MySQL system is referred to as a storage engine (also known as a table type). By default, MySQL comes with a number of different storage engines pre-configured and enabled in the MySQL server. You can select the storage engine to use on a server, database and even table basis, providing you with the maximum amount of flexibility when it comes to choosing how your information is stored, how it is indexed and what combination of performance and functionality you want to use with your data.

This flexibility to choose how your data is stored and indexed is a major reason why MySQL is so popular; other database systems, including most of the commercial options, support only a single type of database storage. Unfortunately the 'one size fits all approach' in these other solutions means that either you sacrifice performance for functionality, or have to spend hours or even days finely tuning your database. With MySQL, we can just change the engine we are using.

In this article, we're not going to concentrate on the technical aspects of the different storage engines (although we will inevitably have to look at some of these elements), instead we will concentrate on how and where these different engines can be best employed. To achieve this, we'll have to look at some of the fundamental issues before moving on to the specifics of each engine type.

Full Article.

More in Tux Machines

Debian-Based Clonezilla Live 2.4.2-29 Is Out with Partclone 0.2.81 and Lots of Bugfixes

On the first day of August 2015, Steven Shiau has released a new testing version of his popular Clonezilla Live CD, which can be used for disk cloning and imaging operations, version 2.4.2-29. Read more

Arch Linux-Based BlackArch Penetration Testing Distro Now Using Linux Kernel 4.1 LTS

The development team behind the BlackArch project, a GNU/Linux distribution derived from Arch Linux and designed to be used for penetration testing and security analysis operations, released an updated installation media, BlackArch 2015.07.31. Read more

Linus Torvalds warns he's in no mood to be polite as Linux 4.2 drags

Linus Torvalds' regular Sunday night missive on the state of kernel development has labelled version 4.2 as a bit of a problem child and warned he “might not react politely” to some developer requests. Announcing the release of release candidate five (rv5), Torvalds says “it's looking like 4.2 might be one of the releases needing more than the usual seven rc releases.” Read more

Simplicity Linux 15.7 Officially Released, Based on LXPup and Linux Kernel 4.1 LTS

As reported at the beginning of July, David Purse, the developer of the Simplicity Linux distribution, announced the release and immediate availability for download of the final version of his Simplicity Linux 15.7 operating system on July 30, 2015. Read more