MySQL 5 InnoDB to MariaDB Migration
-
@GregoryHall and I are working on a migration of an old MySQL 5 InnoDB on CentOS 5 system over to a brand new MariaDB system on Windows Server 2012 R2.
Old system is MySQL 5.0.95
I'm posting this here as we get started on the project. I know that attempts to migrate the system to later versions of MySQL have failed due to complexities in how the database was set up. So there are going to be a lot of challenges that we will post here as we go.
-
What makes mysqldump not an option? Just the sheer size of the database?
-
Complexity. That only works for certain database styles.
-
How is the project going?
I know where were some tools from RedGate, and a couple of other companies that could do similar to this, but I'm not sure if they worked with MySQL / MariaDB
-
@dafyre said:
I know where were some tools from RedGate, and a couple of other companies that could do similar to this, but I'm not sure if they worked with MySQL / MariaDB
Redgate tools are nice. I use their SQL Compare product religiously at one client.
-
@scottalanmiller said:
Complexity. That only works for certain database styles.
Are you able to isolate what patterns in complexity prevent this type of transition? I've used MySQL dumps to migrate what I'd call extremely complex databases with hundreds of tables that if modeled in some kind of large-scale diagram might well resemble a spider web. Interested to know what patterns preclude the successful use of a dump and import.
-
@creayt said:
@scottalanmiller said:
Complexity. That only works for certain database styles.
Are you able to isolate what patterns in complexity prevent this type of transition? I've used MySQL dumps to migrate what I'd call extremely complex databases with hundreds of tables that if modeled in some kind of large-scale diagram might well resemble a spider web. Interested to know what patterns preclude the successful use of a dump and import.
The complexity doesn't come from the tables but from the about of application logic that was put into the database itself. No amount of table complexity would be an issue. This is a problem that we can't find any means of exporting and importing the entire database. It never quite gives you everything.
-
So basically the views, and triggers and stored procedures aren't exporting or is there another level of logic that I'm not aware of yet?
-
@dafyre said:
So basically the views, and triggers and stored procedures aren't exporting or is there another level of logic that I'm not aware of yet?
Views are fine. It's stored procedures and stored functions that are the killers.
-
Ewwww... I ran into that when trying to do something similar with a Great Plains / Dynamics Database ... Ugh.
I feel for you now. How far along ar eyou guys into the process?
-
Not at all, huge fish to fry first.
-
-
Me too, that sounds good now that you say it.
I am staying with my dad too, here in the land of pizza, subs and fish frys.
