To upgrade mysql vesion in workbench - mysql

I am using latest version of workbench The available MySQL version is 5.0.27. Does anybody knows how to update MySQL version?

MySQL Workbench is a client tool that uses an existing server. Both have their own version numbers. The current GA (generally available) version of MySQL Workbench is 6.2.5. For the server there are obviously different versions. You don't need to consider WB when upgrading. Just upgrade your server and WB will happily work with it.
Update
Meanwhile the MySQL group switched to a unique versioning scheme, where all products have the same version number, to indicate which release of a tool works best with which server (e.g. MEB 8.0.15 with MySQL 8.0.15 or MySQL Workbench 8.0.16 with the same versioned server). It makes sense to update all components at the same time to ensure maximum compatibility.

Related

is there an option to configure replication salve of MYSQL version 5.7 to master Azure Database for MySQL of version 5.6?

i have Azure Database for MySQL of version 5.6 in AZURE and i read somewhere that MYSQL support in slave in higher version (5.7) than the master (5.6) but i did not found any reference to it in AZURE doc and did not found any option to configure version when creating replica via AZURE portal , is this possible to configure replica in higher version specifically salve of MYSQL version 5.7 to MYSQL 5.6 master in Azure Database for MySQL ?
Azure Database for MySQL support version 5.6 and 5.7.
You can get all the supported versions and release notes from this document:
Supported Azure Database for MySQL server versions:
MySQL Version 5.6: Refer to the MySQL release notes to learn
more about improvements and fixes in this version.
MySQL Version 5.7: Refer to the MySQL release notes to learn
more about improvements and fixes in this version.
In Azure Database for MySQL,Using dump and restore help you upgrade across MySQL versions. For more details, please see: Common uses for dump and restore
To avoid any compatibility issues, ensure the same version of MySQL is used on the source and destination systems when dumping databases. For example, if your existing MySQL server is version 5.7, then you should migrate to Azure Database for MySQL configured to run version 5.7.
If you don't need to care about the compatibility issues, you can try to use this way to
downgrade and configure the version 5.7 to 5.6.
Hope this helps.

MySQL workbench says bad handshake

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/

how to chose right version of mysql workbench

Upgrading the database version needs intensive testing.
Is it better to upgrade to latest version of MySQL workbench?
If we are installing previous versions of MySQL database, Is there any certification matrix to know all the corresponding version of MySQL workbench or what minimum version it can work with?
Mysql-Workbench using libmysql.dll. You must update this dll from your mysql\lib folder. So a lot function working same as before.

Mysql SET OPTIONS on version 5.6+

Ifter upgrading Mysql server from 5.5 to 5.7 we found that query 'SET OPTION' is deprecated. We asked our system's developers and they said that they are not plannig any updates to support newer mysql versions.
What can we do now? Is there any way to bypass this deprecated query?
I thinking we can set another server instance with version 5.7 replicating from old server 5.5.

Which versions of mysql can MySQL Workbench 6.0.9 connect to?

I've scoured the MySql website to see if they have compatibility listings for MySQL Workbench, but have not found anything. Does anyone know if 6.0.x can connect to 5.5.x databases? I'd rather not install and then have to roll back.
MySQL Workbench can connect to most MySQL server versions, but that is probably not the primary question. You should rather ask what minimum version it can work with. MySQL Workbench requires at least MySQL 5.0 and can work with any MySQL server after that (including the new 5.7). Some features like authentication plugin or performance schema support require higher server versions, though.