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

today's howtos

Security Leftovers

Leftovers: Debian, Ubuntu and Derivatives

  • Debian Developers Make Progress With RISC-V Port
    Debian developers continue making progress with a -- currently unofficial -- port of their Linux operating system to RISC-V. There is a in-progress Debian GNU/Linux port to RISC-V along with a repository with packages built for RISC-V. RISC-V for the uninitiated is a promising, open-source ISA for CPUs. So far there isn't any widely-available RISC-V hardware, but there are embedded systems in the works while software emulators are available.
  • 2×08: Pique Oil
  • [Video] Ubuntu 17.04 KDE
  • deepin 15.4 Released, With Download Link & Mirrors
    deepin 15.4 GNU/Linux operating system has been released at April 19th 2017. I list here one official download link and two faster mirrors from Sourceforge. I listed here the Mega and Google mirrors as well but remember they don't provide direct download. The 15.4 provided only as 64 bit, the 32 bit version has already dropped (except by commercial support). I hope this short list helps you.

Leftovers: OSS and Sharing

  • Overlayfs snapshots
    At the 2017 Vault storage conference, Amir Goldstein gave a talk about using overlayfs in a novel way to create snapshots for the underlying filesystem. His company, CTERA Networks, has used the NEXT3 ext3-based filesystem with snapshots, but customers want to be able to use larger filesystems than those supported by ext3. Thus he turned to overlayfs as a way to add snapshots for XFS and other local filesystems. NEXT3 has a number of shortcomings that he wanted to address with overlayfs snapshots. Though it only had a few requirements, which were reasonably well supported, NEXT3 never got upstream. It was ported to ext4, but his employer stuck with the original ext3-based system, so the ext4 version was never really pushed for upstream inclusion.
  • Five days and counting
    It is five days left until foss-north 2017, so it is high time to get your ticket! Please notice that tickets can be bought all the way until the night of the 25th (Tuesday), but catering is only included is you get your ticket on the 24th (Monday), so help a poor organizer and get your tickets as soon as possible!
  • OpenStack Radium? Maybe…but it could be Formidable
    OK the first results are in from the OpenStack community naming process for the R release. The winner at this point is Radium.
  • Libreboot Wants Back Into GNU
    Early this morning, Libreboot’s lead developer Leah Rowe posted a notice to the project’s website and a much longer post to the project’s subreddit, indicating that she would like to submit (or resubmit, it’s not clear how that would work at this point) the project to “rejoin the GNU Project.” The project had been a part of GNU from May 14 through September 15 of last year, at which time Ms. Rowe very publicly removed the project from GNU while making allegations of misdeeds by both GNU and the Free Software Foundation. Earlier this month, Rowe admitted that she had been dealing with personal issues at the time and had overreacted. The project also indicated that it had reorganized and that Rowe was no longer in full control.
  • Understanding the complexity of copyleft defense

    The fundamental mechanism defending software freedom is copyleft, embodied in GPL. GPL, however, functions only through upholding it--via GPL enforcement. For some, enforcement has been a regular activity for 30 years, but most projects don't enforce: they live with regular violations. Today, even under the Community Principles of GPL Enforcement, GPL enforcement is regularly criticized and questioned. The complex landscape is now impenetrable for developers who wish their code to remain forever free. This talk provides basic history and background information on the topic.

  • After Bill Gates Backs Open Access, Steve Ballmer Discovers The Joys Of Open Data
    A few months ago, we noted that the Gates Foundation has emerged as one of the leaders in requiring the research that it funds to be released as open access and open data -- an interesting application of the money that Bill Gates made from closed-source software. Now it seems that his successor as Microsoft CEO, Steve Ballmer, has had a similar epiphany about openness. Back in 2001, Ballmer famously called GNU/Linux "a cancer". Although he later softened his views on software somewhat, that was largely because he optimistically claimed that the threat to Microsoft from free software was "in the rearview mirror". Not really: today, the Linux-based Android has almost two orders of magnitude more market share than Windows Phone.
  • New Open Door Policy for GitHub Developer Program
    GitHub has opened the doors on its three year old GitHub Developer Program. As of Monday, developers no longer need to have paid accounts to participate. "We're opening the program up to all developers, even those who don't have paid GitHub accounts," the company announced in a blog post. "That means you can join the program no matter which stage of development you're in,"
  • MuleSoft Joins the OpenAPI Initiative: The End of the API Spec Wars
    Yesterday, MuleSoft, the creators of RAML, announced that they have joined the Open API Initiative. Created by SmartBear Software and based on the wildly popular Swagger Specification, the OpenAPI Initiative is a Linux Foundation project with over 20 members, including Adobe, IBM, Google, Microsoft, and Salesforce.