Tricky one, depends on the revision of the server according to the book. MySQL themselves recommend that you piecemeal your way up
the upgrade path if the two databases are on different engine revisions. I found it a little hard getting hold of the intervening
releases between a straight 4 Max and a 5.1, and went all in the deep end. I backed off the /blah/data/ directory of the target
engine, then extracted a tar'd version of the old DB into the right part of the path. There are a couple of executables its
worthwhile running which live in the bin directory for MySQL which check permissions and database integrity.
damn... have to look them up a moment;
Ah yeah, here we go - there is one script which does a pile of checking and optimisation for you all in one
mysql_upgrade (link: http://dev.mysql.com/doc/refman/5.0/en/mysql-upgrade.html)
I found it a bit tricky on the system I had a go with, and instead ran the component parts myself;
mysql_check and
mysql_fix_privilege_tables
I essentially waded through the info page at
http://dev.mysql.com/doc/refman/5.0/en/mysql-upgrade.html
By and large everything seems to have worked, the odd table might have a broken index field, but TBH I'm not certain that they
didn't in the old engine as a result of a sloppy set up by a user.
However, I might have misunderstood the question, when you say you are merging two databases, do you mean also that you are
merging the privs and users?
best wishes
Steve
Web Technical Support Officer
Information Systems Unit
Manchester Metropolitan University
Before acting on this email or opening any attachments you should read the
Manchester Metropolitan University's email disclaimer available on its website
http://www.mmu.ac.uk/emaildisclaimer
|