Recovery of Model in MYSQL/MariaDB database from 2008! (SOLVED)

[Barry_Pearce]

Hi,

Im trying to recover an old model of ours from a MySQL database.
A mysqldump was take prior to a hardware change and Im trying to get it up on the new system as it has some important information on it still.

We now have mariadb. A new database schema was created, with a different name (due to conflict) - although I believe this shouldnt cause an issue.
We have the latest Maridb ODBC connector and configuration a User data source works and tests OK. DBeaver can also use the same ODBC datasource and shows full (appropriate for permissions) access across the database server.
The client is on Windows 10. With EA 12.0

Im seeing EA refuse to connect with invalid data source check configuration.

Does this error also occur if the database is an old format?
I assume I need to upgrade the database to the latest EA standards (2 vers back) will this likely solve the invalid data source issue or is there another problem?

Cheers
Barry

[qwerty]

I doubt this should be an issue. The ODBC settings might be a bit tricky to setup and there are a number of dependencies. Don't know whether 32/64 bit could be an issue (EA is 32 bit). Try connecting with a native client via ODBC.

q.

[Barry_Pearce]

[Solved]
Indeed the problem was the ODBC driver.

Updating to EA 13 didnt help - not surprising.
The MariaDB ODBC driver is not similar (enough) to the MYSQL ODBC driver.
Replaced with the MySQL ODBC driver (still connecting to the MariaDB database) and all has recovered without requiring any additional patching. Now safely transferred to an EAP file.
All good.

[Eve]

The MariaDB ODBC driver is not similar (enough) to the MYSQL ODBC driver.

Unless I'm mistaken, the part that isn't similar enough is that it identifies itself as MariaDB ODBC instead of MySQL ODBC. EA version 13 doesn't know what that driver is, or how to use it. I believe version 14 allows you to use the MariaDB ODBC driver.