By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
458,089 Members | 1,507 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 458,089 IT Pros & Developers. It's quick & easy.

MySql Upgrade, 3.23.41 to 4.X questions.

P: n/a
BDR
Questions for anyone with experience on this topic...

Sit: We're running a standalone server with applications/db's written
around 3.23.41. Linux R/H 7.2 with updates. This is an Apache
production server (currently in operation w/12 co domains) and we're
about to launch new apps using Mysql now that the s/w is complete.

Before we do this, there is a lingering q of whether or not to take
advantage of a 4.x upgrade at this time, before any further sw changes
are made, and our db starts populating with customer data.. etc.

Considering that some `things` take time to iron out from the bug
detector community, does anyone have any advice regarding the following:

1. Which latest version of MySql would be most prudent to download and
install, (least buggy w/o problems that would affect the most simplistic
of issues with our 3.23 designed s/w).

2. Has anyone done an upgrade from 3.23 to 4, and broken their server
or had issues that broke mysql?

3. What if any, headaches encountered doing an upgrade of this sort,
and how to avoid them at all costs.

This all sounds kind of lame to some, but I'm just trying to be careful
and don't want to sabotage my own system while it's working just great
under 3.23.

Thanks to all.

Jul 19 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Hi There,

Yes I did this without any problems and I'm now using 4.0.14 which is
considered the most current/stable version.
But it doesn't install as per the docs. I have to do a rpm install something
like this rpm mysq(whatever).rpm -vHf or something I
found it on google to overwrite the old version of mysql on the machine. If
you are using MyISAM tables it's simple as. If not
then convert them before hand. And definately back it all up before hand.

Thanks

Aaron
"BDR" <jo*@noemail.com> wrote in message
news:3F**************@noemail.com...
Questions for anyone with experience on this topic...

Sit: We're running a standalone server with applications/db's written
around 3.23.41. Linux R/H 7.2 with updates. This is an Apache
production server (currently in operation w/12 co domains) and we're
about to launch new apps using Mysql now that the s/w is complete.

Before we do this, there is a lingering q of whether or not to take
advantage of a 4.x upgrade at this time, before any further sw changes
are made, and our db starts populating with customer data.. etc.

Considering that some `things` take time to iron out from the bug
detector community, does anyone have any advice regarding the following:

1. Which latest version of MySql would be most prudent to download and
install, (least buggy w/o problems that would affect the most simplistic
of issues with our 3.23 designed s/w).

2. Has anyone done an upgrade from 3.23 to 4, and broken their server
or had issues that broke mysql?

3. What if any, headaches encountered doing an upgrade of this sort,
and how to avoid them at all costs.

This all sounds kind of lame to some, but I'm just trying to be careful
and don't want to sabotage my own system while it's working just great
under 3.23.

Thanks to all.

Jul 19 '05 #2

P: n/a
Hi There,

Yes I did this without any problems and I'm now using 4.0.14 which is
considered the most current/stable version.
But it doesn't install as per the docs. I have to do a rpm install something
like this rpm mysq(whatever).rpm -vHf or something I
found it on google to overwrite the old version of mysql on the machine. If
you are using MyISAM tables it's simple as. If not
then convert them before hand. And definately back it all up before hand.

Thanks

Aaron
"BDR" <jo*@noemail.com> wrote in message
news:3F**************@noemail.com...
Questions for anyone with experience on this topic...

Sit: We're running a standalone server with applications/db's written
around 3.23.41. Linux R/H 7.2 with updates. This is an Apache
production server (currently in operation w/12 co domains) and we're
about to launch new apps using Mysql now that the s/w is complete.

Before we do this, there is a lingering q of whether or not to take
advantage of a 4.x upgrade at this time, before any further sw changes
are made, and our db starts populating with customer data.. etc.

Considering that some `things` take time to iron out from the bug
detector community, does anyone have any advice regarding the following:

1. Which latest version of MySql would be most prudent to download and
install, (least buggy w/o problems that would affect the most simplistic
of issues with our 3.23 designed s/w).

2. Has anyone done an upgrade from 3.23 to 4, and broken their server
or had issues that broke mysql?

3. What if any, headaches encountered doing an upgrade of this sort,
and how to avoid them at all costs.

This all sounds kind of lame to some, but I'm just trying to be careful
and don't want to sabotage my own system while it's working just great
under 3.23.

Thanks to all.

Jul 19 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.