Software Update: SQL Server Management Studio 17.8.1

Microsoft has released a new version of SQL Server Management Studio, often abbreviated to SSMS, with version number 17.8.1. With SSMS you can manage a Microsoft SQL environment, for example an on-premise SQL Server, but also an Azure SQL Data Warehouse in the cloud. It offers tools for the configuration, monitoring and commissioning of the various data tier components and you can also build queries and scripts. The corresponding announcement looks like this:

SSMS 17.8.1
A bug was discovered in 17.8 related to provisioning SQL databases, so SSMS 17.8.1 replaces 17.8.

SSMS 17.8

what’s new

• General SSMS
  • Database Properties: This improvement exposes the AUTOGROW_ALL_FILES configuration option for Filegroups. This new config option is added under the Database Properties > Filegroups window in the form of a new column (Autogrow All Files) of checkboxes for each available Filegroup (except for Filestream and Memory Optimized Filegroups). The user can enable/disable AUTOGROW_ALL_FILES for a particular Filegroup by toggling the corresponding Autogrow_All_Files checkbox. Correspondingly, the AUTOGROW_ALL_FILES option is properly scripted when scripting the database for CREATE / generating scripts for the database (SQL2016 and above).
  • SQL Editor: Improved experience with Intellisense in Azure SQL Database when the user doesn’t have master access.
  • Scripting: General performance improvements, especially over high-latency connections.
• Analysis Services (AS)
  • Analysis Services client libraries and data providers updated to the latest version, which added support for the new Azure Government AAD authority (login.microsoftonline.us).

Bug fixes

• General SSMS
  • Maintenance Plans: Fixed an issue when editing maintenance plans with Sql Authentication where “Notify Operator Task” was failing when using SQL authentication.
  • Scripting: Fixed an issue where PostProcess actions in SMO lead to resource exhaustion and SQL login failures
  • SMO: Fixed an issue where Table.Alter() fails if adding a column with a default constraint and the table already has data. For details, see sql server smo generating inline default constraint when adding a column to a table containing data.
  • Always Encrypted: Fixed an issue (in DacFx) which was causing a lock timeout error when enabling Always Encrypted on a partitioned table
• Analysis Services (AS)
  • Fixed an issue that occurred when modifying an OAuth datasource in a Tabular Analysis Services 1400-level compatibility model, which caused the changes in the OAuth tokens to not get updated in the data source.
  • Fixed a crash in SSMS that may have occurred when using some invalid data source credentials or editing data sources that didn’t support Change Data Source migration in Power Query (for example, Oracle) in Analysis Services Tabular 1400-level compatibility models.

Known issues

• Clicking the Script button after modifying any filegroup property in the Properties window, generates two scripts – one script with a USE statement, and a second script with a USE master statement. The script with USE master is generated in error and should be discarded. Run the script that contains the USE statement.
• Some dialogs display an invalid edition error when working with new General Purpose or Business Critical Azure SQL Database editions.
• Some latency in XEvents viewer may be observed. This is a known issue in the .Net Framework. Please, consider upgrading to NetFx 4.7.2.