MySQL Bugs: #12888: Multiple Installations

Bug #12888	Multiple Installations
Submitted:	30 Aug 2005 17:03	Modified:	12 Sep 2005 4:09
Reporter:	Richard de Courtney	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL for Windows: Installer	Severity:	S4 (Feature request)
Version:	4.x	OS:	Windows (WINDOWS 2003)
Assigned to:		CPU Architecture:	Any

Description:
Currently we have 4 seperate MySQL databases installed on our server running off different ports. The installer for Windows only permits installation once and to the default installation directory (i.e. once you have conducted an installation, you cannot install again to a seperate folder and set up a new db).

What would be a great time saver and allow consistant upgrades would be the option of Upgrading the existing installations, together with being able to select which databases are active and which the user would want to upgrade with the current release.

Currently I install the db into the default directory and copy the bin files over to each of the databases, which is not an efficient, tidy and solution expected from an enterprise class piece of software.

How to repeat:
Install DB under windows

Suggested fix:
What would be a great time saver and allow consistant upgrades would be the option of Upgrading the existing installations, together with being able to select which databases are active and which the user would want to upgrade with the current release.

The installer permits to install on no-default directory using custom
option. However only one install instance.

What would be a great, clean and enterprise class installation program, operating similarily to windows update, was a simple front end, that checked for the latest version, offered you the choices to upgrade each active mysql db that was running, cleanly install the latest version, stop and restart each db and return with the result of the install.

Whilst the existing installation routine is pretty simple, I know it would save hours of admin work by people such as myself, to run an update installation programme, and know we were installing the latest version rather than checking the mysql site, downloading, installing to the default directory, stopping each of the db's, copying the bin files over and restarting. When we have 5 db's running on 5 different machines, you can understand the loss in productivity, and the bonus an intelligent downloader and installer would make.

Just a suggestion for what is already a great product!

Posted by developer:
 
Moving this feature request to the MySQL Installer category, since the Config Wizard is gone, for all practical purposes.