DBeaver · MySQL · GUI · MariaDB

DBeaver Community vs a lighter MySQL GUI

pimvdmolen.nl · · ~6 min read

DBeaver Community is a free, Apache 2.0 desktop client that talks to MySQL, MariaDB, PostgreSQL, SQLite, SQL Server, Oracle, and any other engine with a JDBC driver. You look at a lighter GUI when the Java runtime, plugin catalog, and 80-engine navigator are more product than you use, while you still want a local editor, a results grid, and an SSH tunnel on macOS, Windows, or Linux.

License, engines, and what lighter means

Both tools can cost $0. DBeaver Community is Apache 2.0. TabulaSQL is MIT. Neither requires an account for the core SQL workflow. DBeaver Community is an Eclipse Java application with a bundled JDK (current Community builds expect Java 25 or newer). TabulaSQL does not need a separate Java install. That difference shows up in RAM, cold start, and how many preference pages sit between you and a SELECT.

Engine coverage is the other axis. DBeaver Community is a JDBC workbench: if a vendor ships a driver, you can usually add it. TabulaSQL ships three drivers: MySQL/MariaDB on the MySQL protocol, PostgreSQL on port 5432, and a local SQLite file. Connect, browse, query, edit, Explain, and ER diagrams work on all four. Index manager, foreign keys, routines, copy wizard, and the user manager stay deepest on MySQL and MariaDB.

If your week is MySQL 8.4 in Docker, MariaDB 11 on a VPS, and one SQLite fixture file, the extra JDBC catalog does not earn its weight. If you also open SQL Server, Redshift, and DuckDB in the same window, DBeaver Community is built for that mix.

When DBeaver Community is the right tool

Stay on DBeaver Community when the long tail of drivers is the job. Community Edition focuses on relational SQL over JDBC. Jump hosts, SSH agent forwarding, password or public-key tunnels, and URL-style JDBC strings are first-class. Data transfer, ER diagrams, task management, and a large plugin list live in the same window.

Memory use is the trade. Java desktop clients often sit in the hundreds of megabytes after a few result sets. You also accept the DBeaver UI: Database Navigator, separate SQL editor windows, and a driver download prompt the first time you add MySQL or PostgreSQL.

Community Edition is not the NoSQL product. MongoDB, Cassandra, and Redis sit on DBeaver PRO. Pick Community for JDBC engines.

When a smaller GUI covers the same daily work

A lighter client is enough when your path is: open a saved connection, browse tables, run SQL, edit a row, check EXPLAIN, and maybe import a .sql dump. TabulaSQL does that for MySQL 5.7+, MariaDB 10.4+, PostgreSQL, and SQLite files. The MySQL and MariaDB path is tested against MySQL 8.4, MySQL 9.7, and MariaDB 11.

SSH tunnels sit in the New Connection form (key file or password) for MySQL/MariaDB and PostgreSQL, not for SQLite. Saved connections are encrypted on disk. Safe Lock shows the UPDATE or INSERT SQL before a grid write. The command palette is Ctrl/Cmd+P. Optional AI text-to-SQL uses a key you bring (OpenAI, Anthropic, or an OpenAI-compatible URL) and stays local until you click Generate.

You give up JDBC-anything, jump-server SSH, mock data generation, and DBeaver's data compare tools. Recreate connections by hand: host, port, user, password. There is no DBeaver connection importer. HeidiSQL, TablePlus, and Sequel Ace remain other options depending on OS and license; TabulaSQL is one free MIT client, not the only one.

License, OS, SSH, and engines compared

Criterion DBeaver Community TabulaSQL
License Apache 2.0, $0 MIT, $0
OS Windows 10+, macOS 11+, Linux macOS, Windows, Linux
Runtime Bundled Java / Eclipse No Java install
Engines Many via JDBC MySQL, MariaDB, PostgreSQL, SQLite
SSH tunnel Password, key, agent, jump host In-app key or password (not SQLite)
Write preview Confirm dialogs Safe Lock shows the SQL
Account None required for Community SQL None

Price and OS support are measurable. Native feel is not. If you already live in Database Navigator and you need a fourth engine next month, stay. If you want the same MySQL GUI on a Linux laptop and a Windows desktop without keeping a JVM warm, a smaller client is enough.

Recreate a DBeaver MySQL connection in five steps

  1. In DBeaver, open the MySQL (or MariaDB) connection. Note Host, Port (usually 3306), Database, Username, and whether SSH is enabled. If the Main tab uses a JDBC URL, copy host and port out of it. For Docker Compose the host is usually 127.0.0.1 and the published port is whatever you mapped.
  2. Download TabulaSQL from https://tabulasql.com/download and install the build for your OS. On macOS, if Gatekeeper blocks the first launch, right-click the app and choose Open. Windows SmartScreen may warn on an unsigned build.
  3. Choose New Connection. Pick the MySQL/MariaDB driver. Set host 127.0.0.1, port 3306 (or your mapped port), username, and password. For a remote server with no public 3306, enable SSH: bastion host, port 22, SSH user, and a key file or password. Leave SSH off for a machine-local server.
  4. Click Test connection. Error 1045 means the MySQL user or host ('root'@'127.0.0.1' vs 'root'@'localhost') does not match. Error 2002 usually means nothing is listening on that TCP port. Create a mysql user for '%@127.0.0.1' if DBeaver was using a socket or a different bind address.
  5. Open a table in the grid, edit one cell, and turn on Safe Lock. Confirm the UPDATE SQL before it runs. That preview is the daily difference versus a data editor that applies cell edits with a generic confirm dialog.

Saved connections stay on your machine. Export them as a .dbmconn file when you set up a second laptop; there is still no cloud sync. SSH notes for other clients live in MySQL GUI with SSH tunnel.

Keep DBeaver for the long tail of drivers

DBeaver Community remains the default free workbench when you live in JDBC, when one window must reach SQL Server and PostgreSQL and MySQL, or when a jump host is how you reach production. Look at TabulaSQL, or another focused client, when you want less Java, fewer preference pages, and Safe Lock on MySQL and MariaDB grids. Feature lists are on /features. If Workbench is the heavy client you are leaving instead, MySQL Workbench alternatives covers that path.

Frequently asked questions

Yes. DBeaver Community is Apache 2.0 and can connect to MySQL and MariaDB over JDBC at $0. You pay in RAM, Java, and UI complexity, not in a license fee.

No. TabulaSQL drivers are MySQL/MariaDB, PostgreSQL, and local SQLite files. For SQL Server, Oracle, or other JDBC engines, keep DBeaver Community or another multi-engine workbench.

TabulaSQL can open an in-app SSH tunnel with a key file or password for MySQL/MariaDB and PostgreSQL. It does not do jump hosts or SSH agent forwarding. For those, stay on DBeaver Community or run ssh -L yourself and point any GUI at 127.0.0.1 on the forwarded port.