Downloads of v 14.0.17199.0:


Last Update:

12 Oct 2017

Package Maintainer(s):

Software Author(s):

  • Microsoft


sql server management studio ssms admin

SQL Server Management Studio 17.3

This is not the latest version of SQL Server Management Studio 17.3 available.

  • 1
  • 2
  • 3

14.0.17199.0 | Updated: 12 Oct 2017



Downloads of v 14.0.17199.0:



Software Author(s):

  • Microsoft

  • 1
  • 2
  • 3
SQL Server Management Studio 17.3 14.0.17199.0

This is not the latest version of SQL Server Management Studio 17.3 available.

  • 1
  • 2
  • 3

This Package Contains an Exempted Check

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Exemption:

Exempted due to necessary KB update not being available.


Scan Testing Exemption for this package version only:


To install SQL Server Management Studio 17.3, run the following command from the command line or from PowerShell:


To upgrade SQL Server Management Studio 17.3, run the following command from the command line or from PowerShell:


To uninstall SQL Server Management Studio 17.3, 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-server-management-studio -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-server-management-studio -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-server-management-studio installed
    name: sql-server-management-studio
    state: present
    version: 14.0.17199.0
    source: STEP 3 URL

See docs at

chocolatey_package 'sql-server-management-studio' do
  action    :install
  version  '14.0.17199.0'
  source   'STEP 3 URL'

See docs at

    Name: sql-server-management-studio,
    Version: 14.0.17199.0,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller sql-server-management-studio
   Name     = 'sql-server-management-studio'
   Ensure   = 'Present'
   Version  = '14.0.17199.0'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'sql-server-management-studio':
  provider => 'chocolatey',
  ensure   => '14.0.17199.0',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install sql-server-management-studio version="14.0.17199.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 as a trusted package on 12 Oct 2017.


SQL Server Management Studio (SSMS) is an integrated environment for accessing, configuring, managing, administering, and developing all components of SQL Server. SSMS combines a broad group of
graphical tools with a number of rich script editors to provide developers and administrators of all skill levels access to SQL Server. This release features improved compatibility with previous versions of SQL Server,
a stand-alone web installer, and toast notifications within SSMS when new releases become available.

Version Number

This package is versioned using the published build number. The corresponding 'release number' is listed below in the Release Notes section.

Supported SQL Server versions

  • This version of SSMS works with all supported versions of SQL Server 2008 - SQL Server 2017 and provides the greatest level of support for working with the latest cloud features in Azure SQL Database and Azure SQL Data Warehouse.
  • There is no explicit block for SQL Server 2000 or SQL Server 2005, but some features may not work properly.
  • Additionally, SSMS 17.x can be installed side by side with SSMS 16.x or SQL Server 2014 SSMS and earlier.

Supported Operating systems

This release of SSMS supports the following 64-bit platforms when used with the latest available service pack:

  • Windows 10 (64-bit)
  • Windows 8.1 (64-bit)
  • Windows 8 (64-bit)
  • Windows 7 (SP1) (64-bit)
  • Windows Server 2016 *
  • Windows Server 2012 R2 (64-bit)
  • Windows Server 2012 (64-bit)
  • Windows Server 2008 R2 (64-bit)

* SSMS 17.X is based on the Visual Studio 2015 Isolated shell, which was released before Windows Server 2016. Microsoft takes app compatibility seriously and ensures that already-shipped applications continue to run on the latest Windows releases. To minimize issues running SSMS on Windows Server 2016, ensure SSMS has all of the latest updates applied. If you experience any issues with SSMS on Windows Server 2016, contact support. The support team determines if the issue is with SSMS, Visual Studio, or with Windows compatibility. The support team then routes the issue to the appropriate team for further investigation.

$ErrorActionPreference = 'Stop';

$packageName= 'SQL Server Management Studio'
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$fullUrl = ''
$fullChecksum = '0AB0B14F36603D337D332E32EAF63C5FD953A9A0792C6384AC7925F5DEA26244'

$upgradeUrl = ''
$upgradeChecksum = '42F996E6320B59287ED7A2E4921185BC35202598D754B0C973D26520FCEA308D'

$release = '17.3'

# Check if 17.0 is installed so we can get upgrade package instead of full package
$version17 = [version]"14.0.17099.0"
$ssms170 = Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion | Where-Object { $_.DisplayName -eq "SQL Server Management Studio" -and ([Version]$_.DisplayVersion) -ge $version17 }

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

  silentArgs    = "/quiet /install /norestart /log `"$env:TEMP\chocolatey\$($packageName)\$($packageName).MsiInstall.log`""
  validExitCodes= @(0, 3010, 1641)

  softwareName  = "SQL Server Management Studio - $release"
  checksum      = ''
  checksumType  = 'SHA256'

if ($ssms170) {
    Write-Warning "Existing install found, using upgrade installer"
    $packageArgs.url = $upgradeUrl
    $packageArgs.checksum = $upgradeChecksum
} else {
    $packageArgs.url = $fullUrl
    $packageargs.checksum = $fullChecksum

Install-ChocolateyPackage @packageArgs

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
SQL Server Management Studio 18.9.1 15.0.18384.0 138720 Friday, April 23, 2021 Approved
SQL Server Management Studio 18.8 15.0.18369.0 153718 Tuesday, December 22, 2020 Approved
SQL Server Management Studio 18.7.1 15.0.18358.0 82072 Friday, October 30, 2020 Approved
SQL Server Management Studio 18.6 15.0.18338.0 105715 Friday, July 24, 2020 Approved
SQL Server Management Studio 18.5.1 15.0.18333.0 46421 Wednesday, June 17, 2020 Approved
SQL Server Management Studio 18.5 15.0.18330.0 84189 Friday, April 10, 2020 Approved
SQL Server Management Studio 18.4 15.0.18206.0 107896 Tuesday, November 19, 2019 Approved
SQL Server Management Studio 18.3.1 15.0.18183.0 35632 Thursday, October 3, 2019 Approved
SQL Server Management Studio 18.2 15.0.18142.0 132 Thursday, October 3, 2019 Approved

SSMS 17.3

Generally available | Build number: 14.0.17199.0

  • New "Import Flat File" wizard added to streamline the import experience of CSV files with an intelligent framework, requiring minimal user intervention or specialized domain knowledge. For details, see Import Flat File to SQL Wizard.
  • Added "XEvent Profiler" node to Object Explorer. For details, see Use the SSMS XEvent Profiler.
  • Updated waits filtering and categorization in Performance Dashboard historical waits report.
  • Added the syntax check of the "Predict" function.
  • Added the syntax check of the External Library Management queries.
  • Added SMO support for External Library Management.
  • Added "Start PowerShell" support to "Registered Servers" window (requires a new SQL PowerShell module).
  • Always On: added read-only routing support for availability groups.
  • Added an option to send tracing details to the Output Window for "Active Directory - Universal with MFA support" logins (off by default; needs to be turned on in user settings under "Tools > Options > Azure Services > Azure Cloud > ADAL Output Window Trace Level").
  • Query Store:
    • Query Store UI will be accessible even when QDS is OFF as long as QDS have recorded any data.
    • Query Store UI now exposes waits categorization in all the existing reports. This will let customers unlock the scenarios of Top Waiting Queries and many more.
  • Made inclusion of the scripting parameters headers optional (off by default; can be enabled in user settings under "Tools > Options > SQL Server Object Explorer > Scripting > Include scripting parameters header") - Connect item 3139199.
  • Removed "RC" branding.
Bug Fixes

General SSMS

  • XEvent:
    • Fixed issue where SSMS opens only part of the events in .xel file.
    • Improved “Watch Live Data” experience when default database is not 'master' - Connect item 1222582.
  • Always On: Fixed issue where "Restore log backups" may fail with error "The log in this backup set terminates at LSN x, which is too early to apply to the database".
  • Job Activity Monitor: fixed inconsistent icons - Connect item 3133100.
  • Query Store: Fixed Issue where user cannot choose "custom" date range for Query Store reports. Linked to below connect items.
  • Fixed issue where connection dialog doesn't "clear" the most recently used database when saved info has named database and user selects <default>.
  • Object Scripting:
    • Fixed an issue where "Generate database script" not working and throwing an error when the user has a paused DW database on the server, but selected another non-DW database and tried t script it.
    • Fixed issue where the header for scripted Stored Procedures was not matching the script settings, resulting in a misleading script -
      Connect item 3139784.
    • Re-enabled the "Script button" when targeting SQL Azure objects.
    • Fixed issue where SSMS was not allowing scripting for "Alter" or "Execute" on some objects (UDF, View, SP, Trigger) when connected to an Azure SQL database -
      Connect item 3136386.
  • Query editor:
    • Improved intellisense when targeting Azure SQL databases.
    • Fixed an issue where queries failed due to an expired authentication token (Universal Authentication).
    • Improved intellisense when working against Azure SQL databases (particularly, when connecting to Azure SQL Database, the latest T-SQL grammar (140) will be used).
    • Fixed issue where open a query window with a connection to a non-DataWarehouse database on a server would cause all subsequent query windows for that server to DataWarehouse databases to throw various errors about unsupported types/options.
  • Always On:
    • Added seeding mode column to Always On dashboard and AG properties page.
    • Fixed issue where it was not possible to create a Linux AG when primary is on Windows - Connect item 3139856.
  • Fixed several "Out of Memory" issues in SSMS when running queries -
    Connect item 2845190,
    Connect item 3123864.
  • Profiler:
    • Fixed issue were Profiler was not working when targeting SQL 2005.
    • Fixed issue where Profiler was not honoring the "trust server certificate" connection option.
  • Activity Monitor: fixed an issue where Activity Monitor does not work when pointed at SQL Server running on Linux.
  • Fixed an issue with the SMO Transfer class where it wouldn’t transfer External Data Source or External File Format objects, objects of those types should now correctly be included in the transfer.
  • Registered Servers:
    • Enabled multiserver query for UA servers (it will try to use the same token for every UA server in the group).
  • AD Universal Authentication:
    • Fixed issue where Azure AD authentication was not supported.
    • Fixed issue where table/view designer was not working.
    • Fixed issue where "Select Top 1000 rows" and "Edit Top 200 rows" were not working.
  • Database restore: fixed an issue where restore omits the last folder in the path when moving files to an alternate location.
  • Compress wizard:
  • Showplan:
    • Fixed issue where PDW operators were not recognized.
  • Server Properties:
    • Fixed issue with not being able to modify server processor affinity.

Analysis Services (AS)

  • Fixed a number of issues with Deployment Wizard to support tabular 1400 compat-level models and Power Query data sources.
  • Deployment Wizard can now deploy to AS Azure when running from Command line.
  • When using Windows Auth in AS Azure the user will now see the name of the user account in Object Explorer correctly.
Known issues in this 17.3 release:

General SSMS

  • The following SSMS functionality is not supported for Azure AD auth using UA with MFA:
    • Database Engine Tuning Advisor is not supported for Azure AD auth; there is a known issue where the error message presented to the user is a bit cryptic "Could not load file or assembly 'Microsoft.IdentityModel.Clients.ActiveDirectory,…" instead of the expected "Database Engine Tuning Advisor does not support Microsoft Azure SQL Database. (DTAClient)".
  • Trying to analyze a query in DTA results in an error: "Object must implement IConvertible. (mscorlib)".
  • Regressed Queries is missing from the Query Store list of reports in Object Explorer.
    • Workaround: Right-click the Query Store node and select View Regressed Queries.

Integration Services (IS)

  • The [execution_path] in [catalog].[event_messagea] is not correct for package executions in Scale Out. The [execution_path] starts with “\Package” instead of the object name of the package executable. When viewing the overview report of package executions in SSMS, the link of “Execution Path” in Execution Overview cannot work. The workaround is to click “View Messages” on overview report to check all event messages.

Discussion for the SQL Server Management Studio 17.3 Package

Ground Rules:

  • This discussion is only about SQL Server Management Studio 17.3 and the SQL Server Management Studio 17.3 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 Server Management Studio 17.3, 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