Community Edition 6.3.0
Enterprise Edition 6.2.0
Mac OS X
Note: plugin is compatible with Eclipse platform (from 4.2 to 2019-09). Required plugins: gef and draw2d.
EE version includes all features of CE version plus:
|Usually we release a new Minor Community Edition version once per two weeks. Major version is released quarterly (every 3 months). Information about previous releases you can find here.|
All Windows binaries are signed with Symantec Code Sign certificates (confirmed by Microsoft).
All MacOS binaries are signed with Apple Developer ID.
Legal company for code sign certificates is DBeaver Corp.
Tested and verified for MS Windows 7/8/10, Linux and Mac OS X.
DBeaver requires Java 1.8 or higher. Windows and MacOS installers include OpenJDK 11 bundle.
If you are on Mac OS X and you do NOT use PKG installer then you will need to setup Java.
Note: 3rd-party JDBC drivers may have their own system requirements.
Windows installer – run installer executable. It will automatically upgrade version (if needed). Installer doesn’t change any system settings or Java installation. Included JRE will be accessible only for DBeaver.
MacOS PKG – just run it and follow installer pages. JRE 11 is included (and will be accessible only for DBeaver).
MacOS DMG – just run it and drag-n-drop DBeaver into Applications. Make sure you have Java installed. On reinstall do the same (your settings won’t be lost).
Debian package – run
sudo dpkg -i dbeaver-<version>.deb. Then execute “dbeaver &”.
RPM package – run
sudo rpm -ivh dbeaver-<version>.rpm. Then execute “dbeaver &”. Note: to upgrade use “-Uvh” parameter.
ZIP archive – extract archive and run “dbeaver” executable. Do not extract archive over previous version (remove previous version before install). Java must be installed separately.
Upgrade – don’t be afraid to remove previous DBeaver version – your settings won’t be lost. All settings are kept in the separate folder (DBeaverData in user home)
Java notes: if you use Windows or MacOS installer then you don’t need to install Java. Otherwise you will need to setup Java separately. Java 1.8+ must be the default Java version. To validate this run “java -version” in terminal window.
wget -O - https://dbeaver.io/debs/dbeaver.gpg.key | sudo apt-key add - echo "deb https://dbeaver.io/debs/dbeaver-ce /" | sudo tee /etc/apt/sources.list.d/dbeaver.list sudo apt-get update && sudo apt-get install dbeaver-ce
You can use PPA repository to easily install/upgrade DBeaver on Debian Linuxes. Mostly it is the same as regular Debian repo but it is hosted on Launchpad.
sudo add-apt-repository ppa:serge-rider/dbeaver-ce sudo apt-get update sudo apt-get install dbeaver-ce
32-bit versions have been obsoleted in version 6.0.1 and later (because both Java and Eclipse platform no longer support 32 bit).
If you need 32-bit version of DBeaver then you can download version 6.0.0 or earlier or use DBeaver Enterprise (we keep building 32-bit EE version with older Eclipse platform).
You may get latest build (EA version) of DBeaver. Usually it contains all major bug fixes found in current stable version. Just choose the archive corresponding to your OS and hardware from the following folder: EA version downloads.
Community Edition sources, issue tracker, older releases, etc: https://github.com/dbeaver/dbeaver
All recent DBeaver versions are available in archive.
DBeaver CE is free software. You can use it for any purpose with no limitations. This software is provided “as is” without express or implied warranty.
Windows and MacOS installers contain bundled Java Runtime (JRE). It is recommended to use JRE shipped with DBeaver. It won’t break any existing JRE installation, nothing will be copied in the system folders, registry or environment variables. This JRE will be accessible only for DBeaver.
DEB/RPM installers will setup all required components (including JRE) prior to DBeaver installation.
All other versions are just minimal archives that don’t contain the JRE or an installer. Just unzip and start dbeaver executable (if you upgrade from a previous DBeaver version then delete it before upgrade).