As others have noted, MySQL Workbench cannot be used instead of Microsoft SQL Manager to manage Azure SQL (MS-SQL Server, I hate that Microsoft uses generic category names for their products).

If you're considering switching to MySQL (Possibly using Azure MySQL managed database), then please not that unlike MS-SQL Server, you do not need the MySQL Workbench to connect your application to MysQL: just use the correct driver for your stack, and you're all set (if your stack is using the .Net platform, use MySQL Connector/NET from: https://dev.mysql.com/downloads/connector/net/ ).

If you do want to use a graphical interface to maintain your MySQL database, then MySQL Workbench is a great choice, but you are not limited to it - as others have mentioned, there is a plethora of competing graphical database management tools that would work just as well with MySQL - one of the advantages of choosing MySQL for your stack is the huge eco-system that is built around it.

Hello Could you give us a better idea of what Data Base Management System (DBMS) you are using at Azure? MySQL Workbench and Microsoft SQL Server Management Studio (SSMS) are tools developed to exclusively manage MySQL and SQL Server, respectively. If you need to manage multiple DBMS's from a single tool, I sugget you try DBeaver. There are also another alternatives: HeidiSQL, phpMyAdmin, etc. Regarding the DBMS itself, I suggest you stick with SQL Server. In my opinion it's more stable and has more features than MySQL - especially in the Standard and Enterprise editions. Regards, Lawrence

As far as I know, MySQL Workbench doesn't handle Microsoft connections, including Azure, you should try Microsoft solutions such as MS VS Code.

Microsoft provides an application known as Azure Data Studio that runs on Windows, Mac and Linux machines. It provides the ability to manage an Azure SQL database, as well as connecting to standard SQL Server databases. https://docs.microsoft.com/en-us/sql/azure-data-studio/what-is?view=sql-server-ver15

Hi Aashwiin, Looking at your stack (https://stackshare.io/aashwiin82347/my-stack), it seems you are using Azure SQL Databases. I'll infer this is Microsoft SQL Server. Therefore, it certainly makes sense you stick with some of the official Microsoft Tooling to connect to it, query and administer it. You'd only be looking at MySQL Query Workbench, if you were running and connecting to a MySQL Database. - That said, could Azure MySQL (https://docs.microsoft.com/en-us/azure/mysql/overview) be an option for you a this point? MySQL offers great performance. I have been running it at various companies (under AWS/RDS and AWS/Aurora) and have no reason to switch over to anything else. - Decision making-wise, how much do your want your local sql/mysql client to influence/weigh in your architecture/technology decisions, though? This can be a slippery slope. - Alternatively, other clients exist, such as "Table Plus" and allow you to connect, on Mac, to a variety of database servers, including SQL Server. It might be worth giving it a try.