Announcing SQL Server Management Studio -16.4.1 Release
Today, we are very pleased to announce the latest generally-available (GA) quality release of SQL Server Management Studio (SSMS) 16.4.1. This update features new PowerShell cmdlets to help perform SQL Server login management and read/write data, and many improvements/bug fixes addressing 19 Connect Items!
Get it here: Download SSMS 16.4.1 release
- The version number for the latest release is 13.0.15900.1
New in this release
- Fixed an issue where attempting to ALTER/Modify a Stored Procedure fails (Microsoft Connect item #3103831)
- New 'Add-SqlLogin' cmdlet to enable new login management scenarios using PowerShell.(Microsoft Connect item #2588952)
- New 'Read-SqlTableData', 'Read-SqlViewData', and 'Write-SqlTableData' cmdlets to view and write data using PowerShell.(Trello Read-SqlTableData Card)(Microsoft Connect item #2685363)
- Improved support and usability for users connecting to various national clouds.
- Fixed an issue where an Out Of Memory Exceptions were being thrown.(Microsoft Connect item #3062914)(Microsoft Connect item #3074856)
- Fixed an issue where filtering by schema was not a valid filter option.(Microsoft Connect item #3058105)(Microsoft Connect item #3101136)
- Fixed an issue where the Monitor window for a stretched database would not be accessible.
- Fixed an issue where the F1 Help always opened online content. Users can now select whether they prefer online or offline help via the "Set Help Preference" in the Help menu.(Microsoft Connect item #2826366)
- Fixed an issue where scripting out a 1200-level Analysis Services tabular model wouldn’t strip out the password for scripting, even though the server version had (client model object is now sync’d before scripting).
- Fixed an issue where 'SELECT TOP N ROWS' option generated deprecated syntax for the the TOP operator.(Microsoft Connect item #3065435)
- Fixed various layout issues throughout SSMS, including the Login Properties page and Advanced Query Execution Options.(Microsoft Connect item #3058199)(Microsoft Connect item #3079122)(Microsoft Connect item #3071384)
- Fixed an issue where a solution was created automatically whenever a user opened a new query window.(Microsoft Connect item #2924667)(Microsoft Connect item #2917742)(Microsoft Connect item #2612635)
- Fixed an issue where temporal tables could not be expanded in Object Explorer when in system databases.(Microsoft Connect item #2551649)
- Fixed an issue where SSMS runs a query to SELECT @@trancount after executing a batch.(Microsoft Connect item #3042364)
- Fixed an issue in Analysis Services where creating a script from a server's properties page resulted in a hidden connection dialog.
- Fixed an issue where Ctrl+Q would not select the Quick Launch toolbar.
- Fixed an issue where changing the MaxSize of a database using the Server Properties dialog was broken for databases > 2 TB.(Microsoft Connect item #1231091)
- Fixed an issue where the Restore Database wizard wouldn't accept filenames with leading whitespaces:(Microsoft Connect item #2395147)
- Fixed an issue in SSMS where an Analysis Services Server admin after scripting server properties may see a "No permissions" error in the dialog.
- Fixed an issue where the Server Properties page could show the incorrect collation for databases in Azure.
- Fixed an issue where creating a database in Azure threw a ConnectionFailure exception.
- Fixed an issue where SSAS PowerShell scripts wouldn’t work on machine without Analysis Services server instance also installed.
Please visit the SSMS download page for additional details, and to see the full changelog.
Known Issues
The full list of known issues is available in Release notes available here.
Contact us
As always, if you have any questions or feedback, please visit our forum or Microsoft Connect page. You can also tweet our Engineering Manager at @sqltoolsguy on Twitter. We are fully committed to improve the SSMS experience and look forward to hearing from you!
Comments
- Anonymous
September 20, 2016
Alter procedure giving error- Anonymous
September 21, 2016
Hi Nathan, we are aware of this issue regarding altering/modifying of store procedures and this is currently being tracked on: https://connect.microsoft.com/SQLServer/feedback/details/3103831/ssms-2016-16-4-fails-when-attempting-to-alter-modify-a-stored-procedure-syntax-error-in-textheader-of-storedprocedure
- Anonymous
- Anonymous
September 20, 2016
After installing this update SSMS cannot "modify" any of my stored procedures.It just reports "Syntax error in TextHeader of StoredProcedure" - Anonymous
September 21, 2016
The comment has been removed - Anonymous
September 21, 2016
The known issues still points to August notes.- Anonymous
September 21, 2016
Hi Chris, thanks for letting us know. These known issues still apply to 16.4 and we will update this page if are any new changes.
- Anonymous
- Anonymous
September 21, 2016
The comment has been removed - Anonymous
September 21, 2016
Modify / Script Stored Procedure as ALTER is broken in this release.=> Syntax error in TextHeader of StoredProcedure '...'. (Microsoft.SqlServer.Smo). - Anonymous
September 21, 2016
This is confusing. This is the "16.4" release with a version number of "13.0.15800.18" and "16.4" does not appear anywhere in the download page.- Anonymous
November 06, 2016
Ha ha...don't you just love it! Microsoft is usually not bad with things like this like Intel is with their driver versions (their graphics driver versioning has been this way for years, where they have 2 completely different numbers). How hard can it be to just have 1 version number ??
- Anonymous
- Anonymous
September 21, 2016
not usable because https://connect.microsoft.com/SQLServer/feedback/details/3103831/ssms-2016-16-4-fails-when-attempting-to-alter-modify-a-stored-procedure-syntax-error-in-textheader-of-storedprocedure