On Fri, Aug 28, 2009 at 9:18 AM, Shawn Green wrote:
> Hank wrote:
>
>> Hello All,
>> I'm in the process of upgrading my database from 4.1 to 5.0 on CentOS.
>> I've been testing the "mysqlcheck --check-upgrade --auto-repair"
>> command,
>> and on one of my MYISAM tables, it's taking forever to
Hank wrote:
Hello All,
I'm in the process of upgrading my database from 4.1 to 5.0 on CentOS.
I've been testing the "mysqlcheck --check-upgrade --auto-repair" command,
and on one of my MYISAM tables, it's taking forever to upgrade the table.
It has about 114 million rows, and I'm guessing i
Hello All,
I'm in the process of upgrading my database from 4.1 to 5.0 on CentOS.
I've been testing the "mysqlcheck --check-upgrade --auto-repair" command,
and on one of my MYISAM tables, it's taking forever to upgrade the table.
It has about 114 million rows, and I'm guessing it needs to be
You may want to try replication. Setup your replication server as
5.0. That server gives you a chance to play to get things right
without affecting the master server. You'll still need to do a dump to
get the slave up to speed. Once you get everything right, you can
switch over and the sla
Does anyone have experience with upgrading large databases (~500GB each)
from MySQL 4.1 to 5.0? The tables are in InnoDB format. We are using the
Community version.
I've read that it's recommended that you use mysqldump and then restore,
but this is not possible for us, as we cannot have our data
Hello,
I am in an environment that has a bunch of unrelated mysql databases
that exist on one server. I would like to upgrade to mysql 5.0 to take
advantage of the newer features, but I don't want to break existing
functionality. I checked out
http://dev.mysql.com/doc/refman/5.0/en/upgrading-fro
