Upgrading MariaDB on Windows

You are viewing an old version of this article. View the current version here.

General information on upgrade and version coexistence

This section assumes MSI installations. MariaDB (and also MySQL) allows different versions of the product to co-exist on the same machine, as long as these versions are differ either in major or minor version numbers. For example, it is possible to have say MariaDB 5.1.51 and 5.2.6 to be installed on the same machine.

However only single instance of 5.2 can exist. If for example 5.2.7 is installed on the machine where 5.2.6 is already there, installer will just replace 5.2.6 executables with 5.2.7 ones.

Now imagine, that both 5.1 andf 5.2 are installed on the same machine and we want to upgrade database instance running on 5.1 to the new version. In this case special tools are requied. Traditionally, mysql_upgrade is used to accomplish such migration. On Windows, the MySQL upgrade is a manual complicated multiple-step process.

Since 5.2.6 MariaDB Windows distribution includes tools that simplify migration between different versions and also allow migration between MySQL and MariaDB.

Note. Automatic upgrades are only possible for DB instances that run as Windows service.

Upgrade Wizard

This is a GUI tool that is typically invoked at the end of MariaDB installation, if upgradable services are found. The UI allows you to select instances you want to upgrade.

mysql_upgrade_service

This is a command line tool that performs upgrade. The tool requires full administrative privileges (required to start and stop services)

Example usage:

  mysql_upgrade_service --service=MySQL

mysql_upgrade_service accepts a single parameter - name of mysql service and performs all steps to convert MariaDB/MySQL instance running as the service to the current version.

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.