Pragmatic Workbench

This is not the latest version of Pragmatic Workbench available.

2017.1.3 | Updated: 12 Jan 2017



Downloads of v 2017.1.3:


Software Author(s):

  • Pragmatic Works Software

Pragmatic Workbench 2017.1.3

This is not the latest version of Pragmatic Workbench available.

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed


To install Pragmatic Workbench, run the following command from the command line or from PowerShell:


To upgrade Pragmatic Workbench, run the following command from the command line or from PowerShell:


To uninstall Pragmatic Workbench, 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 pragmaticworksworkbench -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 pragmaticworksworkbench -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 pragmaticworksworkbench installed
    name: pragmaticworksworkbench
    state: present
    version: 2017.1.3
    source: STEP 3 URL

See docs at

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

chocolatey_package 'pragmaticworksworkbench' do
  action    :install
  version  '2017.1.3'
  source   'STEP 3 URL'

See docs at

    Name: pragmaticworksworkbench,
    Version: 2017.1.3,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller pragmaticworksworkbench
   Name     = 'pragmaticworksworkbench'
   Ensure   = 'Present'
   Version  = '2017.1.3'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'pragmaticworksworkbench':
  provider => 'chocolatey',
  ensure   => '2017.1.3',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install pragmaticworksworkbench version="2017.1.3" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 12 Jan 2017.


Pragmatic Workbench

BI xPress, DBA xPress, and DOC xPress are all included in this package, our three most popular products. All of the included products come with a 14-day full featured trial or enter your product key for total access (separate download is not needed).

BI xPress

BI xPress speeds up BI development and administration by giving you the ability to quickly build packages, install robust auditing frameworks and helps DBAs deploy packages. See more about BI xPress at

DBA xPress

DBA xPress provides next-generation SQL tools tailored for performance and ease of use when architecting or administering Microsoft SQL Server database systems of all sizes. See more about DBA xPress at

DOC xPress

Offering complete documentation for SQL Server instances, DOC xPress also enables documentation for SSAS, SSIS and SSRS. See more about DOC xPress at

$ErrorActionPreference = 'Stop';

$packageName= 'pragmaticworksworkbench'
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url        = ''

$packageArgs = @{
  packageName   = $packageName
  unzipLocation = $toolsDir
  fileType      = 'EXE'
  url           = $url

  silentArgs    = "/quiet /norestart"
  validExitCodes= @(0, 3010, 1641)

  softwareName  = 'Pragmatic Workbench*'
  checksum = '37A93C1F49FDC6C0B7672CA11367396A8575236715F380295D91BE88E665A7D4'
  checksumType = 'sha256'
  checksumType64 = 'sha256'

Install-ChocolateyPackage @packageArgs
$ErrorActionPreference = 'Stop';

$packageName = 'pragmaticworksworkbench'
$softwareName = 'Pragmatic Workbench*'
$installerType = 'EXE' 

$silentArgs = '/quiet /norestart'
$validExitCodes = @(0, 3010, 1605, 1614, 1641)

$uninstalled = $false
$local_key     = 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*'
$machine_key   = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*'
$machine_key6432 = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*'

$key = Get-ItemProperty -Path @($machine_key6432, $machine_key, $local_key) `
                        -ErrorAction SilentlyContinue `
         | ? { $_.DisplayName -like "$softwareName" }

if ($key.Count -eq 1) {
  $key | % { 
    $file = "$($_.UninstallString)"

    if ($installerType -eq 'MSI') {
      $silentArgs = "$($_.PSChildName) $silentArgs"

      $file = ''

    Uninstall-ChocolateyPackage -PackageName $packageName `
                                -FileType $installerType `
                                -SilentArgs "$silentArgs" `
                                -ValidExitCodes $validExitCodes `
                                -File "$file"
} elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$key.Count matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | % {Write-Warning "- $_.DisplayName"}

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
Pragmatic Workbench 2018.2.4.503 186 Thursday, May 3, 2018 Approved
Pragmatic Workbench 2018.2.3.412-beta 184 Thursday, April 12, 2018 Exempted
Pragmatic Workbench 2018.2.2.302-beta 161 Friday, March 2, 2018 Exempted
Pragmatic Workbench 2018.1.4.208 214 Thursday, February 8, 2018 Approved
Pragmatic Workbench 2018.1.4.129-beta 181 Monday, January 29, 2018 Exempted
Pragmatic Workbench 2018.1.3.122-beta 182 Monday, January 22, 2018 Exempted
Pragmatic Workbench 2018.1.2.1206-beta 187 Wednesday, December 6, 2017 Approved
Pragmatic Workbench 2018.1.1.1030-beta 193 Monday, October 30, 2017 Approved

BI xPress version 2017.1.3

New Features

7814: Date formatting within Monitoring Console Reports are now consistent across all reports
8287: Individual Alerts now included when using the Notification Engine to connect to a BI xPress Server
  • Users must reapply the Notification Engine to their SSIS packages to enable the new behavior of including alerts (warnings and errors) that they have opted to be notified about.
8327: Added Filtering Options to the Package Deployment Wizard
  • Users now have the ability to filter files and folders within the explorer window of the package deployment wizard.

Updated Features

1483: Best Practice Analyzer Report now groups results in a more logical manner
1486: Best Practice Analyzer now groups rules based on which technology it applies to
  • BI xPress orders best practice rules based on technology type first. Making it easier to find applicable rules as user can collapse irrelevant rules.
6832: Visual Studio 2015 extension now supports targeting lower server versions for SSIS packages
  • The BI xPress Visual Studio 2015 Extension now supports usage within SSIS projects with the TargetServerVersion set to SQL Server 2012, 2014, and 2016.


1400: Switching the connection for data generation clears all current content
6699: The Auditing Framework does not log the initial values of variables and parameters
7887: BI xPress Notification Framework settings does not save when clicking finish and restarting Visual Studio
8239: Purging the BI xPress repository when using optional Package or Machine name leaves orphaned executions
8331: Notification Engine's Server Integration does not correctly encode special characters
8333: During a custom installation, the BIxPress Extension will not install if LegiTest Extension is excluded
8688: Fix typo within Auditing Framework activity log message
8715: Report Mover does not retain relative folder structure within target server
8752: After using the SSIS Catalog Import, the Package Performance report throws "Conversion failed when converting from a character string to uniqueidentifier" error
8770: BI xPress Extension no longer throws an error when installed on a machine with just SSDT 2015
8775: Creating a new BI xPress database doesn't update the preferences to reference the new connection string
9199: BI xPress Visual Studio Extension throws an exception upon VS startup regarding licensing

DBA xPress version 2017.1.3

New Features

7825: Schema Inspector's modification scripts now include PRINT statements


7816: Schema Inspector sometimes shows duplicate objects
8776: Schema Inspector generated scripts do not include column changes

DOC xPress version 2017.1.3

New Features

8321: Textual view in lineage analysis can now be exported

Updated Features

7835: Lineage Analysis now extracts dependencies for SQL Agent Job Steps of type SSAS Command, SSAS Query, SSIS Package and T-SQL
8342: SSAS 2016 Provider now supports Azure Analysis Services
  • In order for the SSAS 2016 provider to connect to Azure Analysis Services, users will need to download and install the latest Microsoft Azure Analysis Services Client Libraries


8306: Dependency analysis does not show references to JOIN columns
8708: Lineage Analysis doesn't display for Task Factory's Advanced Derived Column, Advanced Aggregator, Advanced Conditional Split, Dimension Merge, Filter Rows and Unpack Transform
8710: SSIS Packages located in a subfolder are not being included
8780: Snapshot Filtering for SSIS packages stored within SQL Server does not work correctly
9160: Dependency scanner throws "Object Reference" error when scanning SQL Stored Procedures that executes a function assigned to a variable
9251: Stability issues when taking a snapshot containing SSAS Tabular 2016 (compatibility level 1200) databases that use translations
9802: Links are not being shown in textual mode lineage

Workbench version 2017.1.3

Updated Features

7430: Help page now includes a button for each installed product that launches local help documentation
8755: Help documentation for System Requirements, Permissions and Setup for BI xPress, DBA xPress, DOC xPress and LegiTest combined
  • Since BI xPress, DBA xPress, DOC xPress and LegiTest are all installed within the same Workbench installer, including the system requirements, permissions and setup for the other products within each individual help documentation can help with setup

This package has no dependencies.

Discussion for the Pragmatic Workbench Package

Ground Rules:

  • This discussion is only about Pragmatic Workbench and the Pragmatic Workbench 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 Pragmatic Workbench, 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