Downloads:

935,726

Downloads of v 14.0.17177.0:

30,241

Last Update:

08 Aug 2017

Package Maintainer(s):

Software Author(s):

  • Microsoft

Tags:

sql server management studio ssms admin

SQL Server Management Studio

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

14.0.17177.0 | Updated: 08 Aug 2017

Downloads:

935,726

Downloads of v 14.0.17177.0:

30,241

Maintainer(s):

Software Author(s):

  • Microsoft

SQL Server Management Studio 14.0.17177.0

This is not the latest version of SQL Server Management Studio 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, run the following command from the command line or from PowerShell:

>

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

>

To uninstall SQL Server Management Studio, 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.17177.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.17177.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.17177.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.17177.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.17177.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.17177.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.

This package was approved as a trusted package on 08 Aug 2017.

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 (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 platforms when used with the latest available service pack:
Windows 10, Windows 8, Windows 8.1, Windows 7 (SP1), Windows Server 2012 (64-bit), Windows Server 2012 R2 (64-bit), Windows Server 2008 R2 (64-bit)

SSMS 17.0 is based on the Visual Studio 2015 Isolated shell, which was released before Windows Server 2016. Microsoft takes app compatibility very seriously and ensures that already-shipped applications continue to run on the latest Windows releases. Because of this, we do not anticipate that SSMS with all latest updates applied) will encounter issues when running on Windows Server 2016. Customers are advised to contact support, should they encounter any issues with SSMS on Windows Server 2016. Support will then work with customers to determine if the issue is with SSMS or Visual Studio or with Windows compatibility, and route the issue appropriately.


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

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

$fullUrl = 'https://download.microsoft.com/download/C/3/D/C3DBFF11-C72E-429A-A861-4C316524368F/SSMS-Setup-ENU.exe'
$fullChecksum = '8F110A033102C2C375C286189BBA48A01CD0B1288E2771E2C3322A3D621237A1'

$upgradeUrl = 'https://download.microsoft.com/download/C/3/D/C3DBFF11-C72E-429A-A861-4C316524368F/SSMS-Setup-ENU-Upgrade.exe'
$upgradeChecksum = 'E4F6612360C1E1103640EE5C396D8EE8ED9A793EFD52EE3C76F0975CF8F6F23B'

$release = '17.2'

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

$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

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.3.1 15.0.18183.0 34603 Thursday, October 3, 2019 Approved
SQL Server Management Studio 18.2 15.0.18142.0 35 Thursday, October 3, 2019 Approved
SQL Server Management Studio 18.1 15.0.18131.0 98689 Friday, June 14, 2019 Approved
SQL Server Management Studio 18.0 15.0.18118.0 84402 Monday, April 29, 2019 Approved
SQL Server Management Studio 17.9.1 14.0.17289.1 340989 Wednesday, November 28, 2018 Approved
SQL Server Management Studio 17.9 14.0.17285.0 81184 Thursday, September 13, 2018 Approved
SQL Server Management Studio 17.8.1 14.0.17277.0 54099 Tuesday, July 10, 2018 Approved
SQL Server Management Studio 17.7 14.0.17254.0 47668 Friday, May 11, 2018 Approved

This article provides details about updates, improvements, and bug fixes for the current and previous versions of SSMS. Download previous SSMS versions below.

SSMS 17.2

Generally available | Build number: 14.0.17177.0

Enhancements
  • Multi-Factor Authentication (MFA)

    • Multiple-user Azure AD authentication for Universal authentication with Multi-factor authentication (UA with MFA)
    • A new user credential input field was added for Universal Authentication with MFA to support multi-user authentication.
  • The connection dialog box now supports the following 5 authentication methods:

    • Windows Authentication
    • SQL Server Authentication
    • Active Directory - Universal with MFA support
    • Active Directory - Password
    • Active Directory - Integrated
  • Database export/import for DacFx wizard using Universal Authentication with MFA.

  • For API support, see IUniversalAuthProvider Interface.

  • ADAL managed library used by Azure AD Universal Authentication with MFA was upgraded to 3.13.9 version.

  • In addition a new CLI interface was delivered supporting Azure AD admin setting for SQL Database and SQL Data Warehouse.

    For more information on the Active Directory authentication methods, see Universal Authentication with SQL Database and SQL Data Warehouse (SSMS support for MFA) and Configure Azure SQL Database multi-factor authentication for SQL Server Management Studio.

  • Output window has entries for queries run during expansion of Object Explorer nodes

  • Enabled View designer Azure SQL Databases

  • The default scripting options for scripting objects from Object Explorer in SSMS have changed:

    • Previously, the default on a new install was to have the generated script target the latest version of SQL Server (currently SQL Server 2017).
    • In SSMS 17.2 a new option has been added: Match Script Settings to Source. When set to True, the generated script targets the same version, engine type, and engine edition as the server the object being scripted is from.
    • The Match Script Settings to Source value is set to True by default, so new installs of SSMS will automatically default to always scripting objects to the same target as the original server.
    • When the Match Script Settings to Source value is set to False, the normal scripting target options will be enabled and function as they did previously.
    • Additionally, all the scripting options have been moved to their own section - Version Options. They are no longer under General Scripting Options.
  • Added support for National Clouds in "Restore from URL"

  • QueryStoreUI reports now supports additional metrics (RowCount, DOP, CLR Time etc.) from sys.query_store_runtime_stats.

  • IntelliSense is now supported for Azure SQL Database

  • Security: connection dialog will default to not trusting server certificates and to requesting encryption for Azure SQL DB connections

  • General improvements around support for SQL Server on Linux:

    • Database Mail node is back
    • Addressed misc issues related to paths
    • Activity Monitor is more stable
    • Connection Properties dialog displays correct platform
  • Performance Dashboard server report now available as a default report:

    • Can connect to SQL Server 2008 and newer versions.
    • Missing indexes sub-report uses scoring to assist in identifying most useful indexes.
    • Historical wait stats sub-report now aggregates waits be category. Idle and sleep waits filtered out by default.
    • New Historical latches sub-report.
  • Showplan node search allows searching in plan properties. Easily look for any operator property such as table name. To use this option when viewing a plan:

    • Right-click on plan, and in the context menu click on Find Node option
    • Use CTRL+F
Analysis Services (AS)
  • New AAD role member selection for users without email addresses in AS Azure models in SSMS
Integration Services (IS)
  • Added new column ("Executed Count") to the execution report for SSIS
Known issues in this release:
  • Query windows using "Active Directory - Universal with MFA Support" authentication may experience an error similar to the following, when attempting to execute a query after being open for one hour:

    Msg 0, Level 11, State 0, Line 0 The connection is broken and recovery is not possible. The client driver attempted to recover the connection one or more times and all attempts failed. Increase the value of ConnectRetryCount to increase the number of recovery attempts.

    Re-running the query should get past the error and succeed.

  • The following SSMS functionality is not supported for Azure AD auth using Universal Authentication with MFA:

    • The New Table/View designer shows the old-style login prompt, and does not work for Azure AD authentication.
    • The Edit Top 200 Rows feature doesn't support Azure Ad authentication.
    • The Registered Server component does not support Azure AD authentication.
    • The Database Engine Tuning Advisor is not supported for Azure AD authentication. There is a known issue where the error message presented to the user is less than helpful: 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).

AS

  • Object Explorer in SSAS will not show the Windows Auth username in AS Azure connection properties.
Bug fixes

Analysis Services (AS)

  • Fixed an issue where AS Restore Database would fail with an error if the DB had a different Name than ID
  • Fixed an issue causing the DAX query window to disregard the menu option for toggling IntelliSense Enabled
  • Fixed an issue that prevented connecting to SSAS through msmdpump IIS http/https addresses
  • Allow connecting to AS Azure using a password that contain a semi-colon
  • Scripting out AS Restore Database command with "Skip Membership" option will include the new corresponding JSON option when used with SQL Server 2017 AS server or AS Azure
  • Fixed an extremely rare issue that could cause the delete database dialog to raise an error when loading
  • Fixed an issue that may occur when attempting to view partitions in 1400-compat level model containing a mix of SQL query and M partition definitions

Integration Services (IS)

  • Fixed issue where the execution information reports of SSISDB catalog can't be displayed
  • Addressed issues in SSMS related to poor performance with large number of projects/packages

Discussion for the SQL Server Management Studio Package

Ground Rules:

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