InnoDB is a storage engine for MySQL relational databases, which is used by widespread PHP-driven software applications like Joomla 3 and Magento. It is ideal for scalable apps, since it performs amazingly well when handling large amounts of data. Rather than locking the whole table to insert new information in a database as many other engines do, InnoDB locks only one row, so it can perform much more tasks for the same length of time. Also, InnoDB offers a faster database failure recovery and supports transactions and foreign key constraints – rules that specify how data inserts and updates should be treated. If a given task has not been fully completed for any reason, the action will be rolled back. Thus, the content in the database will be preserved safe and sound and will not be partially mixed with newly appended content.

InnoDB in Hosting

While InnoDB is either not available or a paid upgrade with many hosting providers, it is an essential part of the standard set of services that we are offering with our hosting packages. If you’d like to make use of a script-powered app that requires InnoDB specifically, in order to be activated and to perform properly, you won’t experience any problems because the InnoDB database engine is available on our in-house developed cloud hosting platform. Irrespective of whether you set up a brand-new database and activate an application manually or use our one-click application installer instrument, InnoDB will be selected automatically by our platform as the default engine if the application requires it instead of MyISAM. In addition to the incredible database failure recovery offered by InnoDB, we also keep regular backups of all databases, so that we can swiftly recover any MySQL database in your shared website hosting account.

InnoDB in Semi-dedicated Servers

If you set up a new MySQL database through the hosting Control Panel provided with all our semi-dedicated server plans and you begin installing a PHP script-driven web application either manually or using our 1-click application installer, the MySQL database storage engine will be selected automatically on the basis of the requirements of the given app. As InnoDB is available on the cloud platform where your new semi-dedicated server account will be set up, it will be set as the default engine for any application that requires it without any manual action needed on your end at any point. To avoid any risk of losing information if you update an app or if you erase a database by accident, we’ll perform backups of all your MySQL databases each day, so if anything happens, we can recover your content.

InnoDB in VPS Servers

If you acquire a VPS server from our company, you will be able to take full advantage of our custom-built Hepsia Control Panel to manage your web content. A Hepsia-equipped Virtual Private Server will permit you to manage any open-source script-driven web app that needs InnoDB, as the database storage engine is an integral part of the default software package that will be pre-installed on the Virtual Private Server during its creation. When you create a brand-new MySQL database using the hosting Control Panel, you will simply have to begin installing an application – manually or using our application installer. InnoDB will be set as the default engine given that the app in question requires it, so you won’t need to do anything else in your VPS account. In the same manner, if a certain application needs MyISAM, it will be automatically set as the default engine for this specific MySQL database.

InnoDB in Dedicated Servers

When you order a new dedicated server, you will be able to pick one of the 3 Control Panels offered by us – Hepsia, cPanel and DirectAdmin. Any server ordered with Hepsia comes with InnoDB pre-installed, so you will not need to add this MySQL database engine manually to be able to run script-powered web apps that need it. InnoDB is used by scalable apps and since a dedicated server will give you all the resources that you require to run large-scale websites, it’s quite likely that you will use InnoDB. You will be able to make use of other engines too, so if a specific app needs MyISAM rather than InnoDB, you will not need to deal with any impediment while managing it. The engine that will be used will be automatically detected when the app installation procedure commences, so you won’t have to change any settings manually at any moment.