upgrading from 4.1 to 5.4
am 01.10.2009 18:30:53 von monem mysql
--001485f6cbaed89f140474e22b79
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Hello
I have to upgrade many mysql databases from mysql 4 and 4.1 to 5.4 with a
large size 2.7 TB
All tables use the MyISAM engine.
I have to make that update on live system with minimal down time possible.
The official method takes too much time. But I=92ve read that we can use =
=91*dump
and reload=92* to upgrade directly to 5.1, will it work with 5.4?
Also the tables contain many charset? Will they be altered?
It's first time that I do that.
Are there any better solution and any precaution to take?
thanks for your help.
monem
--001485f6cbaed89f140474e22b79--
RE: upgrading from 4.1 to 5.4
am 01.10.2009 20:54:58 von Gavin Towey
Using mysqldump and loading directly into 5.4 *might* work, but you should =
never do any of this on your production system without testing.
Get another box, start with 4.1 and do the upgrade on a test server -- even=
test your queries as there a few incompatible changes between 4 and 5. On=
e you know the exact steps you need to take, and how much time it takes, th=
en you can plan the upgrade accordingly on your live system.
Regards,
Gavin Towey
-----Original Message-----
From: monem mysql [mailto:monem.mysql@gmail.com]
Sent: Thursday, October 01, 2009 9:31 AM
To: mysql@lists.mysql.com
Subject: upgrading from 4.1 to 5.4
Hello
I have to upgrade many mysql databases from mysql 4 and 4.1 to 5.4 with a
large size 2.7 TB
All tables use the MyISAM engine.
I have to make that update on live system with minimal down time possible.
The official method takes too much time. But I've read that we can use '*du=
mp
and reload'* to upgrade directly to 5.1, will it work with 5.4?
Also the tables contain many charset? Will they be altered?
It's first time that I do that.
Are there any better solution and any precaution to take?
thanks for your help.
monem
The information contained in this transmission may contain privileged and c=
onfidential information. It is intended only for the use of the person(s) n=
amed above. If you are not the intended recipient, you are hereby notified =
that any review, dissemination, distribution or duplication of this communi=
cation is strictly prohibited. If you are not the intended recipient, pleas=
e contact the sender by reply email and destroy all copies of the original =
message.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgcdmg-mysql-2@m.gmane.o rg
Re: upgrading from 4.1 to 5.4
am 02.10.2009 11:34:38 von Joerg Bruehe
Hi!
I don't do DBA work, so my info may be incomplete:
monem mysql wrote:
> Hello
>=20
>=20
> I have to upgrade many mysql databases from mysql 4 and 4.1 to 5.4 =
with a
> large size 2.7 TB
>=20
> [[...]]
>=20
>=20
> The official method takes too much time. But I've read that we can =
use '*dump
> and reload'* to upgrade directly to 5.1, will it work with 5.4?
I am not aware of any significant difference between 5.1 and 5.4 in t=
he
MyISAM area, so there are good chances that experiences with 5.1 are
applicable to 5.4 as well. (InnoDB would be a different matter.)
>=20
> Also the tables contain many charset? Will they be altered?
Going from 4.0 or 4.1 to 5.1 and up brings you all the changes in
charset / collation handling, but there should be no additional
difference between 5.1 and 5.4 AFAIK.
>=20
> [[...]]
>=20
> Are there any better solution and any precaution to take?
I second Gavin's advice: Do a test migration and check the most
important ones of your applications. Pay special attention to "strang=
e"
characters outside the ASCII range.
HTH,
Jörg
--=20
Joerg Bruehe, MySQL Build Team, Joerg.Bruehe@Sun.COM
Sun Microsystems GmbH, Komturstraße 18a, D-12099 Berlin
Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Wolf Frenkel
Vorsitzender des Aufsichtsrates: Martin Haering Muenchen: HRB1610=
28
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgcdmg-mysql-2@m.gmane.o rg