Downloads of v 14.0.17254.0:


Last Update:

11 May 2018

Package Maintainer(s):

Software Author(s):

  • Microsoft


sql server management studio ssms admin

SQL Server Management Studio 17.7

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

14.0.17254.0 | Updated: 11 May 2018



Downloads of v 14.0.17254.0:



Software Author(s):

  • Microsoft

SQL Server Management Studio 17.7 14.0.17254.0

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

This Package Contains an Exempted Check

1 Test Passing and 1 Exempted Test

Validation Testing Passed

Verification Testing Exempt:

Exempted due to necessary KB update not being available.

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


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


To uninstall SQL Server Management Studio 17.7, 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.17254.0
    source: STEP 3 URL

See docs at

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

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

See docs at

    Name: sql-server-management-studio,
    Version: 14.0.17254.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.17254.0'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

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

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install sql-server-management-studio version="14.0.17254.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 11 May 2018.


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 = '78591C090A91256CCBEBD871DD77EC1677436FC5CEB87560C914C6921D176FBD'

$upgradeUrl = ''
$upgradeChecksum = 'B841B8B4EAAF01FC9860E6D5817A5EF9F8B477C6E14362B03EE5276CDB47D223'

$release = '17.7'

# 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.7.1 15.0.18358.0 81993 Friday, October 30, 2020 Approved
SQL Server Management Studio 18.6 15.0.18338.0 105581 Friday, July 24, 2020 Approved
SQL Server Management Studio 18.5.1 15.0.18333.0 46291 Wednesday, June 17, 2020 Approved
SQL Server Management Studio 18.5 15.0.18330.0 82533 Friday, April 10, 2020 Approved
SQL Server Management Studio 18.4 15.0.18206.0 107332 Tuesday, November 19, 2019 Approved
SQL Server Management Studio 18.3.1 15.0.18183.0 35453 Thursday, October 3, 2019 Approved
SQL Server Management Studio 18.2 15.0.18142.0 111 Thursday, October 3, 2019 Approved
SQL Server Management Studio 18.1 15.0.18131.0 99019 Friday, June 14, 2019 Approved
SQL Server Management Studio 18.0 15.0.18118.0 84518 Monday, April 29, 2019 Approved

SSMS 17.7

Release number: 17.7<br>
Build number: 14.0.17254.0<br>
Release date: May 09, 2018

What's new

General SSMS

Replication Monitor:

  • Replication monitor now supports registering a listener for scenarios where publisher database and/or distributor database is part of Availability Group. You can now monitor replication environments where publisher database and/or distribution database is part of Always On.

Azure SQL Data Warehouse:

  • Add Rejected Row Location support for External Tables in Azure SQL Data Warehouse.

Integration Services (IS)

  • Added a scheduling feature for SSIS packages deployed to Azure SQL Database. Unlike SQL Server on premises and SQL Database Managed Instance (Preview), which have SQL Server Agent as a first-class job scheduler, SQL Database does not have a built-in scheduler. This new SSMS feature provides a familiar user interface that's similar to SQL Server Agent for scheduling packages deployed to SQL Database. If you're using SQL Database to host the SSIS catalog database, SSISDB, you can use this SSMS feature to generate the Data Factory pipelines, activities, and triggers required to schedule SSIS packages. You can then edit and extend these objects in Data Factory. For more info, see Schedule SSIS package execution on Azure SQL Database with SSMS. To learn more about Azure Data Factory pipelines, activities, and triggers, see Pipelines and activities in Azure Data Factory and Pipeline execution and triggers in Azure Data Factory.
  • Support for SSIS package scheduling in SQL Agent on SQL Managed instance. It is now possible to create SQL Agent jobs to execute SSIS packages on the managed instance.
Bug fixes

General SSMS

Maintenance Plan:

Always On:

  • Fixed an issue where Always On Latency Dashboard was not working with SQL Server 2012.


  • Fixed an issue where scripting stored procedure against Azure SQL Data Warehouse, is not working for non-admin user.
  • Fixed an issue where scripting a database against Azure SQL Database was not scripting the SCOPED CONFIGURATION properties.


  • Fixed issue where SSMS crashes then trying to connect to a server, after opting out of sending telemetry.

Azure SQL Database:

  • Fixed an issue where the user was not able to set or change compatibility level (the drop-down from empty). Note: in order to set the compatibility level to 150, the user still needs to use the Script button and manually edit the script.



  • Perf improvement: reduced volume of intellisense queries for column data. This is especially beneficial when working on tables with huge number of columns.

SSMS User settings:

  • Fixed an issue where the options page was not resizing properly.


  • Improved how text is displayed on Statistics details page.

Integration Services (IS)

  • Better support for Azure SQL Database Managed Instance.
  • Fixed an issue where the user was unable to create a catalog for SQL Server 2014 or before.
  • Fixed two issues with reports:
    • Removed the machine name for Azure servers.
    • Improved handling of localized object name.
Known issues

Some dialogs display an invalid edition error when working with new General Purpose or Business Critical Azure SQL Database editions.

download SSMS 17.6

Build number: 14.0.17230.0<br>
Release date: March 20, 2018

Chinese (People's Republic of China) | Chinese (Taiwan) | English (United States) | French | German | Italian | Japanese | Korean | Portuguese (Brazil) | Russian | Spanish

What's new

General SSMS

SQL Database Managed Instance:

  • Added a support for Azure SQL Database Managed Instance. Azure SQL Database Managed Instance (preview) is a new flavor of Azure SQL Database, providing near 100% compatibility with SQL Server on-premises, a native virtual network (VNet) implementation that addresses common security concerns, and a business model favorable for on-premises SQL Server customers.
  • Support for common management scenarios like:
    • Create and alter databases.
    • Backup and restore databases.
    • Importing, exporting, extracting and publishing Data-tier Applications.
    • Viewing and altering Server properties.
    • Full Object Explorer support.
    • Scripting database objects.
    • Support for SQL Agent jobs.
    • Support for Linked Servers.
  • Learn more about Managed Instances here.

Object Explorer:

  • Added settings to not force brackets around names when dragging & dropping from Object Explorer to Query Window. (User suggestions 32911933, and 32671051.)

Data Classification:

  • General improvements and bug fixes.

Integration Services (IS)

Bug fixes

General SSMS

Data Classification:

  • Fixed an issue in Data Classification which was causing newly added classifications to be displayed with stale information type and sensitivity label.
  • Fixed an issue where Data Classification was not working when targeting a server set to a case-sensitive collation.

Always On:

  • Fixed an issue in AG Show Dashboard where clicking on Collect Latency Data could result in an error when the server was set to a case-sensitive collation.
  • Fixed an issue where SSMS was incorrectly reporting an AG as Distributed when the Cluster service shuts down.
  • Fixed an issue when creating AG using Create Availability Group dialog the ReadOnlyRoutingUrl is required.
  • Fixed an issue when the primary is down and manually failover to secondary, a NullReferenceException will be thrown.
  • Fixed an issue when creating Availability Group using backup/restore to initialize a database, on the secondary replicas, the database files will be created in the default directory. The fix includes:
    • Add the data/log directory validator.
    • Only do the file relocation when the replica is on a different OS to the primary replica.
  • Fixed an issue where SSMS wizard doesn't generate CLUSTER_TYPE option, causing secondary join to fail.


  • Fixed issue where trying to upgrade SSMS by installing the "upgrade package" was failing when SSMS was installed in a non-default location.


  • Fixed performance issue where scripting tables on SQL Server 2016 and above could take up to 30 seconds (now, it's down to less than 1 second).

Object Explorer:

  • Fixed an issue where SSMS could throw an exception like "Object cannot be cast from DBNull to other types" when trying to expand Management node in Object Explorer.
  • Fixed an issue where Start PowerShell was not detecting the SQLServer module when user-defined PS profile emitted output.
  • Fixed an intermittent hang that could occur when right-clicking a Table or Index node in Object Explorer.

Database Mail:

  • Fixed an issue where Database Mail Configuration Wizard was throwing an exception when trying to display/manage more than 16 profiles.

Analysis Services (AS)

  • Fixed as issue where modifying a data source on a 1400 compatibility level model in SSMS the changes are not saved to the server.

Integration Services (IS)

  • Fixed an issue where SSMS did not show SSIS catalog node and reports when connected to SQL Database Managed Instance
Known issues

> There is a known issue where SSMS 17.6 becomes unstable and crashes when using Maintenance Plans. If you use Maintenance Plans, do not install SSMS 17.6. Downgrade to SSMS 17.5 if you already installed 17.6 and this issue is affecting you.

Discussion for the SQL Server Management Studio 17.7 Package

Ground Rules:

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