Pragmatic Workbench

This is a prerelease version of Pragmatic Workbench.

2017.2.3.330-beta | Updated: 30 Mar 2017



Downloads of v 2017.2.3.330-beta:


Software Author(s):

  • Pragmatic Works Software

Pragmatic Workbench 2017.2.3.330-beta

This is a prerelease version of Pragmatic Workbench.

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.2.3.330-beta
    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.2.3.330-beta'
  source   'STEP 3 URL'

See docs at

    Name: pragmaticworksworkbench,
    Version: 2017.2.3.330-beta,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller pragmaticworksworkbench
   Name     = 'pragmaticworksworkbench'
   Ensure   = 'Present'
   Version  = '2017.2.3.330-beta'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'pragmaticworksworkbench':
  provider => 'chocolatey',
  ensure   => '2017.2.3.330-beta',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install pragmaticworksworkbench version="2017.2.3.330-beta" 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 as a trusted package on 30 Mar 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 = '00556FF17C0EAAE3030875EC98FD8941430236A3E885DA8851CC18E9498E19D3'
  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.2.3.330-beta

New Features

9070: MaxVarCharsToLog has been parameterized and configurable when viewing within the Monitoring Console
9176: Purge Database Wizard offers a start and end date instead of Days To Start and Days To Keep
  • The purge database wizard now offers users a start date and an end date to constrict the purging of SSIS Package Executions. The underlying stored procedure remains the same and has not changed, only the user experience. For those that need to determine the DaysToStart and DaysToKeep parameters for SQL Agent Jobs or stored procedures, hovering over the start and end date boxes within the UI will provide that data.
9178: Snippet Wizard is now available when right-clicking in the Control Flow or Event Handlers view of BI xPress SSDT Extension

Updated Features

9148: BI xPress Help File now includes addtional info on BI xPress database updates
9179: Auditing Framework within Workbench now includes validation warnings
9246: The "View Packages in Visual Studio" button is no longer available
9838: Package Builder Wizard's "New Template (From Selection)" and "Modify Packages (From Selection)" now available in Visual Studio 2015
9864: Snippet Wizard's help documentation now includes note that it only operates on one SSIS package at a time
10313: Package Deployment's help documentation now includes limitation on being unable to deploy packages to the SSIS Package Catalog
10337: Quick Status View is now available in BI xPress Visual Studio 2015 Extension


9150: "An Item with the same key has already been added" error when applying the auditing framework to a package that contains identically named components
9177: Modifications by BI xPress may not be applied correctly if there are unsaved changes within SSDT 2016 / Visual Studio 2015.
9197: Data Flow Tasks for some packages are not showing the row counts
9258: Project files are no longer included in the selected packages list when right-clicking on a project within BI xPress Extension for Visual Studio 2015
9259: Error: Unable to cast object of type 'System.Collections.ObjectModel.Collection'1[PW.Common.AuditWarning]' to type 'System.Collections.Generic.List'1
9827: Deployment Wizard persists previously selected packages
9851: Variables values are now appearing correctly when viewing the package execution during and after execution.
9863: BI xPress Add-in does not show the correct SSIS version for packages when selecting an SSIS Project that uses TargetServerVersion
9866: The Variable Expression buttons disappear when changing the Grid Settings to show all package variables
10252: Package and Project Parameters aren't being accessed when Notificaton Engine is applied to SSIS packages
10279: When browsing for existing BI xPress databases from within the Workbench Plugin, selecting a different server changes the existing database name and may throw a "cannot connect" warning
10286: Package executions imported from the SSIS Catalog are not seen as the same package in the Monitoring Console Dashboards
10301: Within SSIS 2005 and 2008, Deployment Wizard throws 'Overload resolution failed because no accessible "PopulateMSDBPackagesInfo"...' error
10322: Using a touch screen with the Monitoring Dashboard causes Workbench to crash.
10325: Error report submission fails with redirect message
10326: Could not apply auditing framework to lower version packages with SSDT 2015 installed
10327: Applying the Auditing Framework from Workbench causes "Can not log connection. Re-applying BIxPress Auditing Framework may fix this issue" warning during execution
10347: "Latest x executions" not showing more than the latest 20 entries when x is > 100,000
10348: Entering over 10,000,000,000 executions in the Options menu of Monitoring Dashboard crashes the Workbench
10349: Monitoring Dashboard doesn't show any packages when you select the "Ungrouped" group in the Group Filtering
10366: Marking a package execution as stopped does not update the control flow and data flow tasks
10373: Using package parameters for Package Deployment projects uses the BI xPress database specified in the wizard, not the server/database/username/password defined in the connection manager.
10977: In the Package & Task Performance report, when Execution Mode is set to anything other than "Interactive" it throws "An error occurred when retrieving the report data: Value cannot be null. Parameter name: s" error
11073: When "Object Variable Logging" is disabled, applying the Auditing Framework throws a "Failed to create OnVariableChanged handler: Value does not fall within the expected range"

DBA xPress version 2017.2.3.330-beta


4711: The correct row counts are not displayed when comparing results from two tables that share the same binary(32) or varbinary(32) key

DOC xPress version 2017.2.3.330-beta

Updated Features

8244: SQL Server Provider can now snapshot an Availability Group's secondary databases when they are set to Read-intent only
9254: Documentation now includes SSAS Tabular translations


9229: Large data dictionary imports fail to process
9800: Timestamp in Snapshot Management History in UTC instead of local time
9801: Solutions do not load alphabetically
9824: When connecting to an HTTPS Report Server DOC xPress throws "The provided URL scheme 'https' is invalid; expected 'http'. Parameter name: via" error
9849: Lineage Analysis' High detail cannot be selected for large solutions
10277: Object types in SSIS may not be correctly recognized in foreign language installations
10280: When scanning a Tableau view, DOC xPress throws a "Given key was not present in the dictionary" error
10352: Lineage does not respect refinements when extending items
10353: Calculated measures missing from SSAS documentation in certain circumstances
10974: SSIS provider does not find Microsoft.VisualStudio.Tools.Applications when snapshotting an older version IS package under SSDT for Visual Studio 2015
11016: Global entry values in the data dictionary cannot be over-ridden
11083: An Object Reference Error sometimes occurs when switching from grid view to list view

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