DBeaver

DBeaver Community Edition is free and open source under Apache License 2.0, which permits use, modification, and redistribution subject to the license terms. That makes the Community edition suitable for personal, educational, and commercial database work without purchasing a paid edition. The open-source package includes core desktop database management, SQL editing, data browsing, connection handling, and diagram tools. Commercial editions add capabilities intended for organizations that need broader cloud, NoSQL, security, collaboration, or enterprise functions. Companies should still review the Apache 2.0 license and any separate licenses that apply to database drivers, database servers, or third-party components used alongside the client before defining internal redistribution or deployment policies.

The Community edition supports a broad range of relational, analytical, cloud, and other data sources through database drivers. Its official project list includes PostgreSQL, MySQL, MariaDB, Microsoft SQL Server, Oracle, SQLite, Firebird, DB2, DuckDB, ClickHouse, Snowflake, Redshift, BigQuery, Databricks, Trino, Teradata, and many additional platforms. JDBC is the primary connectivity mechanism, so a database with a compatible JDBC driver can often be configured even without a dedicated preset. Drivers may be bundled, downloaded automatically, or added manually through Driver Manager. Exact capabilities vary by database because metadata models, SQL dialects, authentication methods, transaction behavior, and native administration utilities differ significantly between vendors and driver implementations.

Current desktop distributions include the Java runtime they need, so most Windows users do not have to install Java separately. The official download documentation states that distributions since version 23.0 include an OpenJDK 21 bundle and that current releases require Java 21 or higher. Bundling the runtime simplifies setup because the application can start with a compatible Java environment instead of depending on a separately maintained system installation. Advanced users can choose their own compatible Java installation by changing the setup and removing the bundled runtime directory as documented. This requirement applies to the database client itself and is separate from any Java software needed by database servers, development tools, or other applications.

The application can display and edit records through its Data Editor when the connected database, account permissions, and result set allow updates. Tables and views can open in a grid, while SQL query results appear in a similar editing environment. Users can filter, sort, inspect individual values, and apply supported changes without manually composing every statement. The SQL Editor remains available when explicit INSERT, UPDATE, DELETE, or database-specific commands are more appropriate. Actual editability depends on the driver, object type, available keys, transaction mode, and privileges granted by the database. Read-only connections or non-updatable result sets remain restricted, so users should verify connection settings and permissions before attempting direct changes to production data.

DBeaver can be updated on Windows by running the newer official installer, which is designed to upgrade an existing installation while preserving settings kept in the separate user data location. The project also provides ZIP packages, but its documentation advises against extracting a new archive directly over an older extracted version. Archive users should replace the old program directory while retaining their separate configuration data. Before updating a work system, close active editors and ensure important scripts or transactions are saved. Community maintenance releases are published frequently, generally on a two-week cycle, so checking the official download page or release notes is the safest way to confirm the latest stable build and review database-specific fixes.