I am running MySQL Workbench on Ubuntu 12.04. MySQL workbench cannot use FreeTDS for migration of MSSQL 2000 to MYSQL, it wants to use iODBC. I cannot find a deb/ubuntu MS SQL 2000 ODBC connector that I can use with iODBC.
All the documentation assumes you are running MySQL Workbench under Windows. I tried that, but had too many issues. Based on 3 days to googeling, trial and error, I think it will work better with MySQL Workbench running the migration from Ubunto instead of Windows.
Does anyone know of an ODBC driver for Ubuntu that will work with MySQL Workbench/iODBC?
Thanks!
JR
To clarify: iODBC is NOT a driver, is a driver manager. FreeTDS is a driver and you need both to use migration wizard. All detailed instructions how to setup you can find in link below:
Installing a driver for Microsoft SQL Server and Sybase ASE in Linux and Mac
The MySQL migration forum contains a number of sticky links to various resources that may help you with your task.
How-To, Blog post
List of links to ODBC drivers for various RDBMSes (and MS Access)
Related
I tried connecting the database from the server, but MySQL Workbench says that the connection cannot be made and declaring it as Bad Handshake. Can someone help me with this? But if I use the same user id and password and DB connections, it works on the other computer systems. Can someone solve this issue?
The authentication has changed from mysql V8, you must use a compatible client and server.
BTW it's a bug : https://bugs.mysql.com/bug.php?id=91828
Here is a workaround without uninstalling the new workbench.
The most probable case is having an old server with a new workbench:
get the server version
From a SQL cli tool:
SHOW VARIABLES LIKE "%version%";
or from a cli connected on the server:
$ mysql -v
It should show a version < 8.0, in my case 5.1.73
Get the mysqlWorkbench for a version <8.0:
You cannot install the msi if you already have a workbench V8.0, so you have to choose a portable installation form a zip file here:
https://dev.mysql.com/downloads/workbench/6.1.html
Select the version 6.2.5 (last before v8.0) zip version
Unzip
Close the workbench v.8 (it lock any other workbench launch)
Launch the V6.2.3 version of workbench, it should works.
This is probably because of a mismatch in the versions of MySQL servers.
Check the version of the MySQL server you are trying to connect to, and the version you have installed on the computer you are using, they have to be the same.
The reason of this warning is version problem. If you have installed mysql server version <= 5.1 and your remote server mysql version is greater than that you will face this problem. I recommend you to install 5.7 or greater in both your local and remote server. This problem will be fixed.
Fortunately there is an easy way around this. Use the old MYSQL ADMINISTRATOR tool as shown below. In my case I was trying to open a MySQL 5.1 database for a clients WordPress installation with MySQL Workbench 8 and that did not work out :).
ALl credits goes to https://www.urtech.ca/2019/01/solved-bad-handshake-mysql-workbench-failed-to-connect-to-sql/
Follow this link for the details
https://www.urtech.ca/2019/01/solved-bad-handshake-mysql-workbench-failed-to-connect-to-sql/
I managed to connect to 192.168.0.253 with MySQL ODBC 3.51 Driver installed using Control Center but when I switch to Work Bench, it gives me the following error, Malformed Packet
If I use the Control Centre I am good to connect. Please help
WorkBench
Control Center
This MySQL server version is way too old. MySQL Workbench currently supports MySQL server 5.6, 5.7 and 8.0.
I have a MySQL database with several gigabytes of data I want to analyse. I have installed SPSS 22 and I am trying to get it to connect to MySQL using the ODBC Data Source Administrator. It seems fine with Access, MS SQL etc, but I can't get it to connect to MySQL.
I'm using XAMPP 32bit on a Windows 7 64 bit machine. I've installed:
http://dev.mysql.com/downloads/connector/odbc/ (installing the 32bit version to match the version of MySQL)
And when I set up the connections in Win7 Administrative tools -> ODBC Data Course Administrator and I can't see any way to register a MySQL ODBC connection
Am I missing something?
EDIT:
As the OS is 64 bit it requires a 64 bit ODBC connector. Installing the 64 ODBC connector allows me to build a connection, but as the database is 32 bits we get a mismatch and it won't connect.
"architecture mismatch"
Solution would be to install a 64 bit version of XAMPP, but they don't seem to build them
In Windows, there is a link table feature in SQL Server (or MS Access). Basically, if I link SQL-Server and MySQL, then when my apps write something in SQL-Server, the MySQL is also updated via ODBC connection.
Basically the flow is: win-apps -> sql-server 2008 -> (via win-odbc) mysql (linux)
Now I want to reverse the process in Linux environment into:
the flow I want is: nix-apps -> mysql (linux) -> (via nix-odbc?) sql-server 2008...
Is this possible?
If you want to connect to SQL Server from unixODBC there are a couple of options commercially Easysoft SQL Server ODBC driver or if you prefer an un-supported free version the Free TDS ODBC driver
Other ODBC drivers are available but may not be compatable with unixODBC.
I've a mysql database with version 3.23 installed on linux server.
When i try to use the database using sql yog, it will connect.But when i try to connect to the database using mysql work bench installed on windows xp, i will get an error.
Screen shots are below :
When i tried to connect mysql with the help of SQL YOG,
When i try to connect mysql with MySQL workbench
I used Putty to check whether SSH port 22 is listening or not, it is listening.. I can see the terminal.. an i checked host of root login...
I tried connecting with the help of SSH, i didnt get the solution... I am not able to track where i am getting wrong...
Can any one help me out???
Thanks in advance...
Regards,
Anoop Pete
Your server version is just not supported:
MySQL Workbench fully supports MySQL Server versions 5.1 and above. It
is also compatible with MySQL Server 5.0, but not every feature of 5.0
may be supported. It does not support MySQL Server versions 4.x.
Sadly, MySQL 3.23 is almost 12 years old.