How to Use DBeaver: The Beginner's Guide (First Connection, First Query, and the Test-Before-You-Finish Rule)

CodexFuse Team · 2026-10-30T05:52:32.285Z · 10 min read

Install DBeaver Community Edition, create your first database connection, test it before you finish, and run your first SQL query — a beginner's guide.

How do you actually use DBeaver?

Learning how to use DBeaver comes down to five moves: install the free Community Edition, pick your database driver, create a connection, test it before you finish the wizard, and run a limited SELECT in the SQL editor. Everything else DBeaver offers — ER diagrams, data export, SSH tunnels — sits on top of that loop.

DBeaver is a free, open-source universal database client: one desktop app that connects to PostgreSQL, MySQL, SQLite, SQL Server and dozens more database engines through standard JDBC drivers. If you currently write SQL inside a code editor, our VS Code beginner guide covers the editor branch — DBeaver is the database-client branch, where the connection, the schema browser and the result grid all live in one window.

1. Install Community Edition with the installer for your OS (Windows exe, macOS DMG, Linux deb/rpm), not the ZIP archive.
2. Open the New Database Connection wizard — it appears automatically on first launch, or via Database → New Database Connection (Ctrl+N).
3. Pick your driver from the gallery and let DBeaver download it when it offers; every database type needs its driver installed once.
4. Fill in host, port, database, username and password, then click Test Connection — never click Finish on an untested connection.
5. Open a SQL script, write a limited SELECT, and press Ctrl+Enter to run it; rows appear in the result grid with timing in the status bar.

What is DBeaver, and which edition should a beginner install?

The short answer: install DBeaver Community Edition and ignore the paid editions until you outgrow them. Community Edition is free and open source under the Apache License 2.0 — the product's own Community hub states it plainly, and the same line is confirmed by the DBeaver Wikipedia entry, which notes the community edition has been Apache-licensed since version 4.x (2017). It includes the Database Navigator, SQL Editor, Data Editor, ER diagrams, data transfer tools and database maintenance utilities.

The commercial line is branded DBeaver PRO and currently ships as Lite, Enterprise and a top-tier Ultimate edition, plus CloudBeaver for browser access and a CLI called dbvr. An independent October 27, 2026 comparison of database tools confirmed DBeaver Community costs nothing while listing the top DBeaver paid edition at $510 per user per year — for contrast, DataGrip sells at $229 and TablePlus team seats at $79. A beginner's entire first year of DBeaver runs on the free edition; PRO exists for NoSQL, cloud-native and exotic data sources that a beginner rarely meets.

Version numbers move monthly, so download the newest Community build rather than memorizing one. Trackers show Community 26.2.3 as the newest build (released October 18, 2026, per Wikipedia's release tracker and confirmed by the October 27, 2026 independent comparison), while some community guides still walk through 26.1.5 — either way, you are in the 26.2.x line as of this writing. The Windows installer runs around 108 MB, the macOS DMG around 118 MB and the Linux deb around 122 MB, per third-party mirror listings for 26.2.3. And you do not need to install Java yourself: DBeaver's official packages have bundled their own runtime since version 23.0 (the community guides confirm it needs Java 25 or higher and ships it), so a fresh machine runs the installer and opens the app.

How do you install DBeaver on Windows, Mac, and Linux?

Download the Community Edition installer for your OS from the official download page and run it — the whole install is a standard next-next-finish wizard. Choose the edition carefully on that page: it now presents the PRO lineup first, so scroll to the Community Edition download to get the free one.

• Windows: run the x86_64 exe installer (around 108 MB). Prefer the installer over the ZIP — the community guides warn that SmartScreen reputation warnings hit fresh ZIP builds hardest, and an installer registers the app properly.
• macOS: open the DMG (aarch64 or x86_64, around 118 MB) and drag DBeaver into Applications.
• Linux: install the deb (Debian/Ubuntu) or rpm (Fedora/RHEL) package, around 122 MB — the package manager handles updates afterward.

Two rules from the community guides keep installs clean. First, never overwrite an old install by unzipping a new release over the old tree — run the new installer or extract the new ZIP to a fresh directory. Second, your connections are safe across upgrades: settings and connection profiles live in a separate DBeaverData folder in your user directory, so removing the application directory does not remove your saved connections.

How do you create your first database connection in DBeaver?

Open the New Database Connection wizard: Database → New Database Connection in the menu, the plug icon in the toolbar, or Ctrl+N. On a first-ever launch DBeaver opens the wizard automatically. The official docs list all three routes, so use whichever you find first.

1. Pick your driver in the driver gallery. Tabs on the left split the list into All, Popular, SQL, NoSQL and Analytical — the Popular tab holds the drivers most people use daily — or just type the first letters into the search box.
2. Download the driver when DBeaver offers it. DBeaver does not ship every JDBC driver in the box; the first time you connect to a database type it prompts you to download that driver's files. Accept the download once per database type and you will never see the prompt for it again.
3. Fill in the connection settings. For server databases the wizard asks for host, port, database name, username and password. For embedded engines like SQLite it only asks for the file path — pick an existing database file or create a new one.
4. Click Test Connection. This is the rule the rest of this guide is named after: test every connection before you finish the wizard. A green test result means the host, port, credentials and driver all agree; a red one tells you which of those four to fix.
5. Click Finish. The connection appears in the Database Navigator tree on the left and DBeaver actually connects — expand it to see schemas, tables and views.

The most common first-connection failure is a firewall or a wrong host/port, not DBeaver itself — the community troubleshooting guide lists wrong host/port, driver mismatch, firewall and missing SSH tunnel parameters as the four usual causes. If you are connecting to a database running on your own machine and do not have a server yet, our Docker beginner guide walks through spinning one up locally.

First-connection cheat sheet: ports and fields per database

The wizard pre-fills the standard port for each driver, so most beginners only type the host, the database name and their credentials. The table below lists what each of the four most common first connections needs:

Two things to remember about this table. First, the driver download happens once per database type, not once per connection — connect to three different PostgreSQL servers and you download the driver exactly once. Second, these are defaults: if your host uses a non-standard port, type it in; the Test Connection button exists precisely to catch that mistake before it becomes a broken saved connection.

How do you run your first SQL query in DBeaver?

Right-click your connection in the Database Navigator, open a new SQL script, and write a limited SELECT — LIMIT is the beginner's seatbelt because it stops a first query from dumping a million rows into the grid. A safe first query looks like this:

SELECT id, first_name, last_name
FROM customers
ORDER BY id
LIMIT 20;

Press Ctrl+Enter to run the current statement or the selected text — this is DBeaver's core shortcut and the one the community first-query checklist names. Rows land in the result grid below the editor, and the status bar notes how long the fetch took. Highlight part of a script and hit Ctrl+Enter to run just that part, which is how you test a WHERE clause before committing to the full query.

Before running a query you copied from somewhere, run it through a SQL formatter so you can actually read what it does — pasted SQL with collapsed line breaks is where beginners introduce syntax errors they cannot see. And keep an eye on the result grid's row count: if a query returns far more rows than you expected, your LIMIT or WHERE clause is doing less work than you think.

When do you need an SSH tunnel in DBeaver?

You need an SSH tunnel when the database server refuses direct connections — typical for databases on cloud VMs or company networks where only SSH (port 22) is open. DBeaver handles this natively: open the connection's settings, go to the Network Settings tab, and configure the SSH tunnel with the same credentials you would use in a terminal SSH session. Supported authentication methods include user/password, public-key authentication and agent authentication (pageant and ssh-agent), per the official documentation.

The order matters: fill in the required database parameters (host, port, user, database) first, then set up the tunnel, then test. The community guides specifically warn to set the database parameters before testing the tunnel — a tunnel test against blank database settings fails in a way that looks like an SSH problem but is really an empty-form problem. If the test passes, finish the wizard and DBeaver routes all database traffic through the tunnel automatically.

How do you export data from DBeaver?

Data transfer is a Community Edition feature — the product's Community overview lists it alongside the SQL Editor and ER diagrams, so you never need a paid edition for basic exports. Right-click any table in the Database Navigator, or any result set in the grid, and choose Export Data; the wizard walks you through format choices (CSV for spreadsheets, SQL INSERT scripts for moving data between servers) and lets you pick which columns and rows go out.

For exports you repeat — a weekly CSV pull, a nightly backup extract — save the export as a data-transfer task so the column mappings and format choices survive. The community best-practices guide recommends saved data-transfer tasks exactly for this: one saved task replaces a screenshot of settings you would otherwise have to re-enter every time.

DBeaver Community vs PRO vs DataGrip: what should a beginner actually pay for?

Nothing — that is the honest answer for the first year. DBeaver Community is the free, open-source universal client, and its October 2026 state covers relational databases end to end: connections, SQL editing, ER diagrams, data transfer and maintenance tools. The PRO editions add NoSQL support, certain cloud databases and team features; they exist for shops with exotic stacks, not for learning SQL.

The paid-alternative math is worth knowing once. The October 27, 2026 independent comparison that confirmed Community 26.2.3 as the newest build also priced the field: DBeaver's top paid edition at $510 per user per year, JetBrains DataGrip at $229, and TablePlus team seats at $79 each. Every one of those is a fine tool, but none of them changes the beginner arc — install Community, connect, test, query. If your data lives behind an HTTP API rather than a database, that is a different tool family entirely: our Postman beginner guide covers the API-client branch the way this guide covers the database-client branch.

Sources

• DBeaver Community guides — install, first-query checklist, connection troubleshooting and upgrade rules (d-beaver.com/guides.html)
• DBeaver official documentation — Create Connection wizard (dbeaver.com/docs)
• DBeaver official tutorial — How to Connect to a Database in DBeaver (dbeaver.com, March 2022)
• DBeaver Community overview — features and edition boundaries (d-beaver.com)
• Liquid Web — DBeaver Tutorial for PostgreSQL, SQLite, MySQL, and MariaDB (liquidweb.com)
• Tech Insider — DBeaver (Free) Beats DataGrip $229 & TablePlus $89 [2026] (tech-insider.org, October 27, 2026)
• Wikipedia — DBeaver (stable release 26.2.3, October 18, 2026; Apache license)
• Software Mirrors — DBeaver Community Edition 26.2.3 downloads (software-mirrors.com)
• Crackuzi — DBeaver for PC: How to Download and Install on Windows, 2026 guide (crackuzi.com)

Frequently asked questions

Is DBeaver really free, or is there a catch?

DBeaver Community Edition is genuinely free and open source under the Apache License 2.0 — no account, no trial clock, no feature-locked basics. The catch, if you want to call it one, is that the download page leads with the paid PRO editions now, so you have to scroll to the Community download to get the free one. The company funds the free edition with commercial PRO licenses, a model it has run since 2017.

Which databases does DBeaver Community support?

Anything with a JDBC driver — in practice PostgreSQL, MySQL, MariaDB, SQLite, Oracle, SQL Server, Firebird and dozens more, which one 2026 guide puts at more than eighty engines. DBeaver downloads each engine's driver automatically the first time you connect to that type. A few exotic sources, mainly NoSQL and certain cloud databases, are reserved for the paid PRO editions.

Why does DBeaver download a driver the first time I connect?

DBeaver is a universal client, so it cannot bundle every database's driver in a 110 MB installer. When you pick a driver in the connection wizard, DBeaver offers to fetch that engine's JDBC files from its driver repository. Accept once per database type; every later connection to the same engine reuses the downloaded files.

Why did my connection test fail even though the settings look right?

Work through the four usual causes in order: wrong host or port, a driver that did not finish downloading, a firewall blocking the port, or a server that only accepts SSH-tunneled connections. The community troubleshooting guide lists exactly these four. Re-open the connection settings, confirm each one, and use Test Connection again before saving — and remember that SQLite connections fail differently (a bad file path) than server connections.

Should I use DBeaver or just keep writing SQL in VS Code?

They solve different halves of the job. VS Code is the better text editor; DBeaver is the better database client — it owns the connection, the schema tree, the result grid with timing, and the export tooling in one window. Most working developers use both: DBeaver to explore data and test queries, the editor to keep the queries that become code.