Downloads:

908,848

Downloads of v 14.0.17213.0:

30,272

Last Update:

12/8/2017

Package Maintainer(s):

Software Author(s):

  • Microsoft

Tags:

sql server management studio ssms admin

SQL Server Management Studio 17.4

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

14.0.17213.0 | Updated: 12/8/2017

Downloads:

908,848

Downloads of v 14.0.17213.0:

30,272

Maintainer(s):

Software Author(s):

  • Microsoft

SQL Server Management Studio 17.4 14.0.17213.0

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

>

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

>

To uninstall SQL Server Management Studio 17.4, 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.17213.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.17213.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.17213.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.17213.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.17213.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.17213.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 12/8/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 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/0/A/E/0AE3B5C9-0D22-4EF3-B48A-73181A7F8EF7/SSMS-Setup-ENU.exe'
$fullChecksum = 'CD174C1C01FCDE5A992A6ACB12A5B21B44F88D595EFE646644E9A4797C52F1C4'

$upgradeUrl = 'https://download.microsoft.com/download/0/A/E/0AE3B5C9-0D22-4EF3-B48A-73181A7F8EF7/SSMS-Setup-ENU-Upgrade.exe'
$upgradeChecksum = 'DEE22963243345EBE96D10019C32D9EF2D31A40FDF2EDBC929ECD2B02E99FD8F'

$release = '17.4'

# 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

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.2 15.0.18142.0 30 Thursday, October 3, 2019 Approved
SQL Server Management Studio 18.1 15.0.18131.0 98655 Friday, June 14, 2019 Approved
SQL Server Management Studio 18.0 15.0.18118.0 84400 Monday, April 29, 2019 Approved
SQL Server Management Studio 17.9.1 14.0.17289.1 339680 Wednesday, November 28, 2018 Approved
SQL Server Management Studio 17.9 14.0.17285.0 81149 Thursday, September 13, 2018 Approved
SQL Server Management Studio 17.8.1 14.0.17277.0 54088 Tuesday, July 10, 2018 Approved
SQL Server Management Studio 17.7 14.0.17254.0 47665 Friday, May 11, 2018 Approved
SQL Server Management Studio 17.6 14.0.17230.0 11339 Friday, March 30, 2018 Approved

SSMS 17.4

Generally available | Build number: 14.0.17213.0

What's new

General SSMS

Vulnerability Assessment:

  • Added a new SQL Vulnerability Assessment service to scan your databases for potential vulnerabilities and deviations from best practices, such as misconfigurations, excessive permissions, and exposed sensitive data.
  • Results of the assessment include actionable steps to resolve each issue and customized remediation scripts where applicable. The assessment report can be customized for each environment and tailored to specific requirements. Learn more at SQL Vulnerability Assessment.

SMO:

  • Fixed issue where HasMemoryOptimizedObjects was throwing exception on Azure.
  • Added support for new CATALOG_COLLATION feature.

Always On Dashboard:

  • Improvements for latency analysis in Availability Groups.
  • Added two new reports: AlwaysOn_Latency_Primary and AlwaysOn_Latency_Secondary.

Showplan:

  • Updated links to point to correct documentation.
  • Allow single plan analysis directly from actual plan produced.
  • New set of icons.
  • Added support for recognize "Apply logical operators" like GbApply, InnerApply.

XE Profiler:

  • Renamed to XEvent Profiler.
  • Stop/Start menu commands now stop/start the session by default.
  • Enabled keyboard shortcuts (for example, CTRL-F to search).
  • Added database_name and client_hostname actions to appropriate events in XEvent Profiler sessions. For the change to take effect, you may need to delete existing QuickSessionStandard or QuickSessionTSQL session instances on the servers - Connect 3142981

Command line:

  • Added a new command line option ("-G") that can be used to automatically have SSMS connect to a server/database using Active Directory Authentication (either 'Integrated' or 'Password'). For details, see Ssms utility.

Import Flat File Wizard:

  • Added a way to pick a schema name other than the default ("dbo") when creating the table.

Query Store:

  • Restored the "Regressed Queries" report when expanding the Query Store available reports list.

Integration Services (IS)

  • Added package validation function in Deployment Wizard, which helps the user figure out components inside SSIS packages that are not supported in Azure-SSIS IR.
Bug fixes

General SSMS

  • Object Explorer:
    • Fixed an issue where Table-Valued Function node was not showing up for database snapshots - Connect 3140161.
    • Improved performance when expanding Databases node when the server has autoclose databases.
  • Query Editor:
    • Fixed an issue where IntelliSense was failing for users that don't have access to the master database.
    • Fixed an issue that was causing SSMS to crash in some cases when the connection to a remote machine was closed - Connect 3142557.
  • XEvent Viewer:
    • Re-enabled functionality to export to XEL.
    • Fixed issues where in some cases the user was not able to load an entire XEL file.
  • XEvent Profiler:
    • Fixed an issue that was causing SSMS to crash when the user did not have VIEW SERVER STATE permissions.
    • Fixed an issue where closing the XE Profiler Live Data window did not stop the underlying session.
  • Registered Servers:
  • SMO:
    • Fixed an issue where the TransferData method on the Transfer object was not working.
    • Fixed an issue where Server databases throws exception for paused SQL DW databases.
    • Fixed an issue where scripting SQL database against SQL DW generated incorrect T-SQL parameter values.
    • Fixed an issue where scripting of a stretched DB incorrectly emitting the DATA_COMPRESSION option.
  • Job Activity Monitor:
    • Fixed an issue where the user was getting an "Index was out of range. Must be non-negative and less than the size of the collection.
      Parameter name: index (System.Windows.Forms)" error when trying to filter by Category - Connect 3138691.
  • Connection Dialog:
    • Fixed an issue where domain users without access to a Read/Write domain controller could not log in to a SQL Server using SQL Authentication - Connect 2373381.
  • Replication:
    • Fixed an issue where an error similar to "Cannot apply value 'null' to property ServerInstance" was displayed when looking at properties of a pull subscription in SQL Server.
  • SSMS Setup:
    • Fixed an issue where SSMS setup was incorrectly causing all the installed products on the machine to be reconfigured.
  • User Settings:
    • With this fix, US Government sovereign cloud users will have uninterrupted access to their Azure SQL Database and ARM resources with SSMS via Universal authentication and Azure Active Directory login. Users of prior versions of SSMS would need to open Tools|Options|Azure Services and under Resource Management change the configuration of the "Active Directory Authority" property to https://login.microsoftonline.us.

Analysis Services (AS)

  • Profiler: fixed an issue when trying to connect using Window Authentication against Azure AS.
  • Fixed an issue that could cause a crash when canceling connection details on a 1400 model.
  • When setting an Azure blob key in the connection properties dialog when refreshing credentials, it will now be visually masked.
  • Fixed an issue in the Azure Analysis Services User selection dialog to show the Application ID guid instead of the Object ID when searching.
  • Fixed an issue in the Browse Database\MDX query designer toolbar that caused the icons to be incorrectly mapped for some buttons.
  • Fixed an issue that prevented connecting to SSAS using msmdpump IIS http/https addresses.
  • Several strings in the Azure Analysis Services User Picker dialog have now been translated for additional languages.
  • MaxConnections property is now visible for data sources in tabular models.
  • Deployment Wizard will now generate correct JSON definitions for Azure AS role members.
  • Fixed an issue in SQL Profiler where selecting Windows Authentication against Azure AS would still prompt for login.

Discussion for the SQL Server Management Studio 17.4 Package

Ground Rules:

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