AU: 1 updated - sql-server-management-studio

[skip ci] https://gist.github.com/7d00c69c2cde8309a8594abaa897a9a6/93a18d697eb39d66406d12b09a1262dc7b65579a

sql-server-management-studio/sql-server-management-studio.nuspec

@@ -3,10 +3,10 @@
 <package xmlns="http://schemas.microsoft.com/packaging/2015/06/nuspec.xsd">
   <metadata>
     <id>sql-server-management-studio</id>
-    <version>14.0.17213.0</version>
+    <version>14.0.17224.0</version>
     <packageSourceUrl>https://github.com/flcdrg/au-packages/tree/master/sql-server-management-studio</packageSourceUrl>
     <owners>flcdrg</owners>
-    <title>SQL Server Management Studio 17.4</title>
+    <title>SQL Server Management Studio 17.5</title>
     <authors>Microsoft</authors>
     <projectUrl>https://docs.microsoft.com/en-us/sql/ssms/sql-server-management-studio-ssms</projectUrl>
     <iconUrl>http://cdn.rawgit.com/flcdrg/au-packages/master/sql-server-management-studio/icons/ssms-icon.png</iconUrl>
@@ -46,96 +46,68 @@ This release of SSMS supports the following 64-bit platforms when used with the
 
 \* 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.	</description>
     <releaseNotes>
-#### [SSMS 17.4](download-sql-server-management-studio-ssms.md)
-Generally available | Build number: 14.0.17213.0
+#### [SSMS 17.5](download-sql-server-management-studio-ssms.md)
+
+Generally available | Build number: 14.0.17224.0
 
 ##### What&apos;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](https://docs.microsoft.com/sql/relational-databases/security/sql-vulnerability-assessment).
+Data Discovery &amp; Classification:
 
-SMO:
-- Fixed issue where *HasMemoryOptimizedObjects* was throwing exception on Azure.
-- Added support for new CATALOG_COLLATION feature.
+- Added a new SQL Data Discovery &amp; Classification feature for discovering, classifying, labeling &amp; 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 &amp; Classification](../relational-databases/security/sql-data-discovery-and-classification.md).
 
-Always On Dashboard:
-- Improvements for latency analysis in Availability Groups.
-- Added two new reports: *AlwaysOn\_Latency\_Primary* and *AlwaysOn\_Latency\_Secondary*.
+Query Editor:
 
-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 &quot;Apply logical operators&quot; 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](https://connect.microsoft.com/SQLServer/feedback/details/3142981)
+- 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. 
 
-Command line:
-- Added a new command line option (&quot;-G&quot;) that can be used to automatically have SSMS connect to a server/database using Active Directory Authentication (either &apos;Integrated&apos; or &apos;Password&apos;). For details, see [Ssms utility](ssms-utility.md).
+Showplan:
 
-Import Flat File Wizard:
-- Added a way to pick a schema name other than the default (&quot;dbo&quot;) when creating the table.
+- Enabled display of estimated plan button for SQL Data Warehouse
+- Added new showplan attribute *EstimateRowsWithoutRowGoal*; and added new showplan attributes to *QueryTimeStats*: *UdfCpuTime* and *UdfElapsedTime*. For more information, see [Optimizer row goal information in query execution plan added in SQL Server 2017 CU3](http://support.microsoft.com/help/4051361).
 
-Query Store:
-- Restored the &quot;Regressed Queries&quot; 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](https://connect.microsoft.com/SQLServer/feedback/details/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&apos;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](https://connect.microsoft.com/SQLServer/feedback/details/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:
-	- Fixed an issue where the &quot;Move To…&quot; command stopped working - [Connect 3142862](https://connect.microsoft.com/SQLServer/feedback/details/3142862) and [Connect 3144359](https://connect.microsoft.com/SQLServer/feedback/details/3144359/).
-- 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 &quot;Index was out of range. Must be non-negative and less than the size of the collection. 
-		Parameter name: index (System.Windows.Forms)&quot; error when trying to filter by Category - [Connect 3138691](https://connect.microsoft.com/SQLServer/feedback/details/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](https://connect.microsoft.com/SQLServer/feedback/details/2373381).
-- Replication:
-	- Fixed an issue where an error similar to &quot;Cannot apply value &apos;null&apos; to property ServerInstance&quot; 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 &quot;Active Directory Authority&quot; 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.
+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 &quot;Input string was not in a correct format. (mscorlib)&quot; when executing a simple query preceded by a &quot;SET SHOWPLAN_ALL ON&quot;. 
+
+
+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 &quot;The multi-part identifier &quot;a.delimited&quot; could not be bound.&quot;
+- 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 &quot;legacy cardinality estimation is not valid scoped configuration&quot; 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 &quot;Cannot assign a default value to a local variable. Must declare the scalar variable &quot;@ServiceStartMode&quot; and, ultimately, was not displaying the SQL Agent node in Object Explorer).
+
+Templates: 
+
+- &quot;Database Mail&quot;: fixed a couple of typos [(https://feedback.azure.com/forums/908035/suggestions/33143512)](https://feedback.azure.com/forums/908035/suggestions/33143512).  
+
+Object Explorer:
+- Fixed an issue where Managed Compression would fail for indexes (https://feedback.azure.com/forums/908035-sql-server/suggestions/32610058-ssms-17-4-error-when-enabling-page-compression-o).
+
+Auditing:
+- Fixed an issue with the *Merge Audit Files* feature.
+&lt;br&gt;
+
+##### 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.&lt;br&gt;
+*Workaround*: Assign the new information type and sensitivity label after the classification was added back to the main view and before saving.
 </releaseNotes>
     <dependencies>
       <dependency id="KB2919355" version="1.0.20160915" />

sql-server-management-studio/tools/chocolateyinstall.ps1

@@ -3,13 +3,13 @@
 $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'
+$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/0/A/E/0AE3B5C9-0D22-4EF3-B48A-73181A7F8EF7/SSMS-Setup-ENU-Upgrade.exe'
-$upgradeChecksum = 'DEE22963243345EBE96D10019C32D9EF2D31A40FDF2EDBC929ECD2B02E99FD8F'
+$upgradeUrl = 'https://download.microsoft.com/download/8/8/3/883FD1FA-FE61-4E83-85F9-FA46D4A5B866/SSMS-Setup-ENU-Upgrade.exe'
+$upgradeChecksum = 'D0DBDC0FC4413854C7040FC3E18CDA3A0E09C4E496F46075215A3C9C5684B33E'
 
-$release = '17.4'
+$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"