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

70-inch Android touchscreen targets interactive education

The CDE7060T is said to offer a Linux OS, but the datasheet more specifically notes that it runs the Linux-based Android 4.2.1 on an unnamed, dual-core Cortex-A9 system-on-chip. Also onboard are 1.5GB of RAM and 8GB of flash. An optional “slot-in” PC is available for greater computing power, says ViewSonic. Pre-installed “ViewBoard” annotation and presentation software allows multiple users to write, draw, or annotate with fingers or styluses simultaneously, says the company. Read more

OpenBSD from a veteran Linux user perspective

For the first time I installed a BSD box on a machine I control. The experience has been eye-opening, especially since I consider myself an "old-school" Linux admin, and I've felt out of place with the latest changes on the system administration. Linux is now easier to use than ever, but administration has become more difficult. There are many components, most of which are interconnected in modern ways. I'm not against progress, but I needed a bit of recycling. So instead of adapting myself to the new tools, I thought, why not look for modern tools which behave like old ones? Read more

Leftovers: KDE Software

  • How KDE VDG Is Trying To Make Open-Source Software Beautiful
    One of the most often voiced complaints about Open Source Software is that it tends to be "ugly" or otherwise aesthetically uninspired. A few years ago a few people in the KDE camp came together and created, what they hoped, would be a solution to that problem: The KDE Visual Design Group.
  • KDE Connect – Insieme, unite unite smartphone
    When I wrote my Kubuntu Vivid review, I mentioned a tool called KDE Connect, which I wasn’t quite sure what it was supposed to be doing. A bunch of you emailed me, telling me it’s a nice little applet that can keep your smartphone notifications in sync with the desktop, as well as allow you to remotely control certain parts of your KDE-flavored desktop from the smartphone.
  • Video review of KDE Plasma 5 from Nerd on the Street
  • Four years later
    At beginning of June 2011 I made my first blog post about KWin support Wayland clients featuring a screenshot of Desktop Grid effect with a Wayland window shown on each desktop.
  • "Private browsing mode" for activities
    The statistics collection feature of KActivities is slowly becoming a core part of Plasma.
  • GSoC update: ocs-server
  • Fun with onion skins
    The first new feature of the GSoC project on animation in Krita is has landed in git. Until now, I have been mostly concentrating on refactoring the core structures toward their final form, which has taken much more time than I anticipated. Fortunately, it is now mostly done, and I am getting to the point where progress is more visible.

Open source COM version of BeagleBone Black hits Kickstarter

A German startup called BeagleCore is spinning a computer-on-module version of BeagleBoard.org’s BeagleBone Black single board computer on Kickstarter. Packages start at 39 Euros ($44) for the first 500 units shipping in Feb. 2016, or 49 Euros ($55) for the second shipment in April. With a baseboard, it costs 99 Euros ($111), also with April 2016 shipment. The BeagleCore and Starter-Kit support Linux flavors including Debian, Ubuntu, Android, and Cloud9 IDE on Node.js with BoneScript library. Read more