When comparing Azure Data Studio vs DBeaver, the Slant community recommends DBeaver for most people. In the question“What are the best MySQL GUI clients for OS X?” DBeaver is ranked 1st while Azure Data Studio is ranked 19th. The most important reason people chose DBeaver is:
Supported on Windows (2000/XP/2003/Vista/7/8/10), Linux, Mac OS and Solaris (x86).
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Supports multiple RDBMSs
PostgreSQL already works; others are in the pipeline:
https://github.com/microsoft/azuredatastudio/issues/56#issuecomment-481007948
Pro Extensible
Pro Customizable server and database dashboards
Pro Code snippets
Pro IntelliSense
Pro Open-source
Pro Cross-platform
Pro Cross-platform
Supported on Windows (2000/XP/2003/Vista/7/8/10), Linux, Mac OS and Solaris (x86).
Pro Free
It is licensed under GPL v2.
Pro Works for many types of databases
MySQL, Oracle, PostgreSQL, IBM DB2, Microsoft SQL Server, Microsoft Access, Sybase, Java DB (Derby), Firebird (Interbase), Derby (JavaDB), SQLite, Mimer, HSQLDB, H2, IBM Informix, Teradata, SAP MAX DB, Cache, Ingres, Linter, Vertica, MongoDB, Cassandra, ODBC, Any JDBC compliant data source.
Pro Follow foreign key to their primary key
If you have a table with a foreign key you can click on it to see the table row where this key references to.
Pro Formatted text view
It has the classic grid view and a well-organized text view that you can quick-select with CTRL-A.
Pro Easy to use, clean neat inteface
Cons
Con Never-ending function errors
Like, 'Communications link failure', 'Connection refused' (Community Edition 6.2.1).
Con Cannot view function
Con Trigger edition
Until version 3.5.8 you can not edit triggers, only view (since 3.5.6).