I have a server with hosted clients, and it's still running MySQL v. 4.1.22. I really should update it, but I'm also thinking "if it ain't broke don't fix it".

Can you guys point me to a list of issues that I may find with the upgrade? Specifically, incompatibilities that I can try to correct before causing a problem for the hosted clients?

On 11/1/2011 5:18 AM, Jason C wrote:
Not from something that old. You'll have to look at the upgrade
comments for each release (i.e. 5.0-5.1, 5.1-5.2, etc.). I don't recall
any major problems when updating, but it's been a long time since I had
any clients running something that old. But you probably should do it
in 2 steps - upgrade to 5.1 then to the latest. This will help minimize
problems.

Basically, use standard practices when updating. Backup all databases
(I highly recommend backing up the entire system also). Update MySQL,
run mysql_update and test. And do it on a test system first, before
updating your production system.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex (AT) attglobal (DOT) net
==================

Jason C <jwcarlton (AT) gmail (DOT) com> wrote:

What is more: you cannot upgrade to the second next major version and
expect all applications to continue working.

RTFM!

4.1 -> 5.0
http://dev.mysql.com/doc/refman/5.0/...us-series.html

5.0 -> 5.1
http://dev.mysql.com/doc/refman/5.1/...us-series.html


I suggest to go to 5.5 directly. A binary upgrade (RTFM what this is)
will very probably not work, so you have to dump and load the data.

I suggest to dump the MySQL accounts with mysqldumpgrants or similar.
Dump all databases except `mysql` with mysqldump. Then load this into
the new installation.


XL