Downloads:

1,446,104

Downloads of v 14.0.17224.0:

27,872

Last Update:

16 Feb 2018

Package Maintainer(s):

Software Author(s):

  • Microsoft

Tags:

sql server management studio ssms admin

SQL Server Management Studio 17.5

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

14.0.17224.0 | Updated: 16 Feb 2018

Downloads:

1,446,104

Downloads of v 14.0.17224.0:

27,872

Maintainer(s):

Software Author(s):

  • Microsoft

Tags:

sql server management studio ssms admin

SQL Server Management Studio 17.5 14.0.17224.0

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

This Package Contains an Exempted Check

1 Test Passing and 1 Exempted Test

Hide Checks
Hide Checks

Validation Testing Passed

Verification Testing Exempt:

Exempted due to necessary KB update not being available.

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

>

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

>

To uninstall SQL Server Management Studio 17.5, 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 https://chocolatey.org/api/v2. 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 https://chocolatey.org/api/v2)

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'"
$exitCode = $LASTEXITCODE

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
  win_chocolatey:
    name: sql-server-management-studio
    state: present
    version: 14.0.17224.0
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

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


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

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: sql-server-management-studio,
    Version: 14.0.17224.0,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


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

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


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

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install sql-server-management-studio version="14.0.17224.0" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

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 16 Feb 2018.

Description

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.

tools\chocolateyinstall.ps1 
$ErrorActionPreference = 'Stop';

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

$fullUrl = 'https://download.microsoft.com/download/8/8/3/883FD1FA-FE61-4E83-85F9-FA46D4A5B866/SSMS-Setup-ENU.exe'
$fullChecksum = '770675775E650BC4B16D26895C5FEE10D1BAF07526762DA46ED0F031CAC418C6'

$upgradeUrl = 'https://download.microsoft.com/download/8/8/3/883FD1FA-FE61-4E83-85F9-FA46D4A5B866/SSMS-Setup-ENU-Upgrade.exe'
$upgradeChecksum = 'D0DBDC0FC4413854C7040FC3E18CDA3A0E09C4E496F46075215A3C9C5684B33E'

$release = '17.5'

# 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.8 15.0.18369.0 97876 Tuesday, December 22, 2020 Approved
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 82535 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 84519 Monday, April 29, 2019 Approved

SSMS 17.5

Generally available | Build number: 14.0.17224.0

What's new

General SSMS

Data Discovery & Classification:

  • Added a new SQL Data Discovery & Classification feature for discovering, classifying, labeling & reporting sensitive data in your databases.
  • Auto-discovering and classifying your most sensitive data (business, financial, healthcare, PII, etc.) can play a pivotal role in your organizational information protection stature.
  • Learn more at SQL Data Discovery & Classification.

Query Editor:

  • Added support for SkipRows option to the Delimited Text External File Format for Azure SQL DW. This capability allows users to skip a specified number of rows when loading delimited text files into SQL DW. Also added the corresponding intellisense/SMO support for the FIRST_ROW keyword.

Showplan:

Bug fixes

General SSMS

Showplan:

  • Fixed Live Query Statistics elapsed time, to show engine execution time instead of time elapsed for LQS connection.
  • Fixed an issue where showplan was not able to recognize Apply logical operators like GbApply and InnerApply.
  • Fixed an issue related to ExchangeSpill.

Query Editor:

  • Fixed on issue related to SPIDs where SSMS could throw an error like "Input string was not in a correct format. (mscorlib)" when executing a simple query preceded by a "SET SHOWPLAN_ALL ON".

SMO:

  • Fixed an issue where SMO was not able to fetch AvailabilityReplica properties in case the server collation happened to be case-sensitive (as a result, SSMS could display an error message like "The multi-part identifier "a.delimited" could not be bound."
  • Fixed an issue in DatabaseScopedConfigurationCollection class, where incorrectly handling collations (as a result, an SSMS running on an ma machine with a Turkish locale could display an error like "legacy cardinality estimation is not valid scoped configuration" when right clicking on a database running on a server with a case-sensitive collation).
  • Fixed an issue in JobServer class, where SMO was not able to fetch SQL Agent properties on a SQL 2005 server (as a result, SSMS was throwing an error like "Cannot assign a default value to a local variable. Must declare the scalar variable "@ServiceStartMode" and, ultimately, was not displaying the SQL Agent node in Object Explorer).

Templates:

Object Explorer:

Auditing:

  • Fixed an issue with the Merge Audit Files feature.
    <br>
Known issues

Data classification:

  • Removing a classification and then manually adding a new classification for the same column results in the old information type and sensitivity label being assigned to the column in the main view.<br>
    Workaround: Assign the new information type and sensitivity label after the classification was added back to the main view and before saving.
Discussion for the SQL Server Management Studio 17.5 Package

Ground Rules:

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