Craig,
It is both feasible and dangerous. Good to hear you plan to put it
through a couple of QA cycles (you will need them), but this can be
accomplished. With a planned downtime window of an hour, I migrated a
couple of terabytes from 4.0 to 5.0 a couple years back while making
numerous schema
Baron Schwartz wrote:
If you can't take downtime, I'd go the slave route.
You should certainly test your application to make sure 5.1's
differences (data types, syntax, etc) don't cause problems. Otherwise
you're risking getting badly stuck and having to downgrade to 4.1
again in a crisis.
If
If you can't take downtime, I'd go the slave route.
You should certainly test your application to make sure 5.1's
differences (data types, syntax, etc) don't cause problems. Otherwise
you're risking getting badly stuck and having to downgrade to 4.1
again in a crisis.
If you dump and reload, you
Hi All,
I need to migrate a large (30G) database from 4.1 to 5.1 on a live
system that cannot afford a large amount of downtime. The official
method (copy files, run mysql_upgrade...etc) is looking like it will
take forever, particularly since I need to move it 5.0 before 5.1. How
do peop
