Downloads of v 124.0.0:


Last Update:

30 Jan 2019

Package Maintainer(s):

Software Author(s):

  • Thomas Kellerer


sql workbench java

SQL Workbench/J

124.0.0 | Updated: 30 Jan 2019



Downloads of v 124.0.0:



Software Author(s):

  • Thomas Kellerer

SQL Workbench/J 124.0.0

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed


To install SQL Workbench/J, run the following command from the command line or from PowerShell:


To upgrade SQL Workbench/J, run the following command from the command line or from PowerShell:


To uninstall SQL Workbench/J, run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade sql-workbench -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade sql-workbench -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure sql-workbench installed
    name: sql-workbench
    state: present
    version: 124.0.0
    source: STEP 3 URL

See docs at

Coming early 2020! Central Managment Reporting available now! More information...

chocolatey_package 'sql-workbench' do
  action    :install
  version  '124.0.0'
  source   'STEP 3 URL'

See docs at

    Name: sql-workbench,
    Version: 124.0.0,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller sql-workbench
   Name     = 'sql-workbench'
   Ensure   = 'Present'
   Version  = '124.0.0'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'sql-workbench':
  provider => 'chocolatey',
  ensure   => '124.0.0',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install sql-workbench version="124.0.0" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved by moderator gep13 on 30 Jan 2019.


SQL Workbench/J is a free, DBMS-independent, cross-platform SQL query tool. It is written in Java and should run on any operating system that provides a Java Runtime Environment.

Its main focus is on running SQL scripts (either interactively or as a batch) and export/import features. Graphical query building or more advanced DBA tasks are not the focus and are not planned.


  • Edit, insert and delete data directly in the query result (Screenshot)
  • Powerful export command to write text files (aka "CSV"), XML, HTML or SQL (including BLOB data). All user tables can be exported into a directory with a single command. Export files can be compressed "on-the-fly".
  • Powerful text, XML and spreadsheet import. A set of files (including compressed files) can be imported from a directory with a single * command. Foreign key constraints are detected to insert the data in the correct order
  • Compare two database schemas for differences. The XML output can be transformed into the approriate SQL ALTER statements using XSLT
  • Compare the data of two database and generate the necessary SQL statements to migrate one to the other.
  • Supports running SQL scripts in batch mode
  • Supports running in console mode (Screenshot)
  • Search text in procedure, view and other sources using a SQL command or a GUI (Screenshot 1 Screenshot 2)
  • Search for data across all columns in all tables using a SQL command or a GUI (Screenshot 1 Screenshot 2)
  • Reformatting (Pretty-Print) of SQL Statements (Screenshot)
  • Select rows from related tables according to their foreign key definitions (Screenshot 1 Screenshot 2).
  • Tooltips for INSERT statements to show the corresponding value or column (Screenshot)
  • Copy data directly between to database servers using a SQL command or a GUI (Screenshot)
  • Macros (aka aliases) for frequently used SQL statements
  • Variable substitution in SQL statements including smart prompting for values (can be combined with macros)
  • Auto completion for tables and columns in SQL statements (Screenshot)
  • Display database objects and their definitions (Screenshot)
  • Display table source (Screenshot)
  • Display view, procedure and trigger source code (Screenshot)
  • Display foreign key constraints between tables (Screenshot)

For more information, see

$ErrorActionPreference = 'Stop'

$url      = ''
$checksum = '3a54f1293524ec792e9abd1c57c7c0509ab42ae914a46bee36d7a1a12abb4603'

$toolsDir = Split-Path -Parent $MyInvocation.MyCommand.Definition

$sqlWorkbench = Join-Path $toolsDir 'SQLWorkbench.exe'
$sqlWorkbench64 = Join-Path $toolsDir 'SQLWorkbench64.exe'
$sqlwbconsole = Join-Path $toolsDir 'sqlwbconsole.exe'
$sqlwbconsole64 = Join-Path $toolsDir 'sqlwbconsole64.exe'

# Create .ignore and .gui files based on OS
if (Get-ProcessorBits -Compare 64) {
  New-Item "$sqlWorkbench.ignore" -Type File -Force | Out-Null
  New-Item "$sqlwbconsole.ignore" -Type File -Force | Out-Null
  New-Item "$sqlWorkbench64.gui" -Type File -Force | Out-Null
} else {
  New-Item "$sqlWorkbench64.ignore" -Type File -Force | Out-Null
  New-Item "$sqlwbconsole64.ignore" -Type File -Force | Out-Null
  New-Item "$sqlWorkbench.gui" -Type File -Force | Out-Null

$packageArgs = @{
  packageName            = $env:ChocolateyPackageName
  unzipLocation          = $toolsDir
  url                    = $url
  checksum               = $checksum
  checksumType           = 'sha256'

Install-ChocolateyZipPackage @packageArgs

# If this is a 64 bit OS, create a secondary shim
if (Get-ProcessorBits -Compare 64) {
  Install-BinFile -Name 'SQLWorkbench' -Path $sqlWorkbench64 -UseStart
  Install-BinFile -Name 'sqlwbconsole' -Path $sqlwbconsole64
$ErrorActionPreference = 'Stop'

$toolsDir = Split-Path -Parent $MyInvocation.MyCommand.Definition

$sqlWorkbench64 = Join-Path $toolsDir 'SQLWorkbench64.exe'
$sqlwbconsole64 = Join-Path $toolsDir 'sqlwbconsole64.exe'

# If this is a 64 bit OS, remove the secondary shim
if (Get-ProcessorBits -Compare 64) {
  Uninstall-BinFile -Name 'SQLWorkbench' -Path $sqlWorkbench64
  Uninstall-BinFile -Name 'sqlwbconsole' -Path $sqlwbconsole64

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status

Discussion for the SQL Workbench/J Package

Ground Rules:

  • This discussion is only about SQL Workbench/J and the SQL Workbench/J package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or SQL Workbench/J, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus