Ask Learn
Preview
Ask Learn is an AI assistant that can answer questions, clarify concepts, and define terms using trusted Microsoft documentation.
Please sign in to use Ask Learn.
Sign inNote
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Today, we are pleased to announce the latest generally-available (GA) quality release of SQL Server Management Studio (SSMS) 16.5.1. This update fixes a couple issues listed below.
Get it here:
- The version number for the latest release is 13.0.16100.1
New in this release
- Fixed an issue where Invoke-Sqlcmd erroneously inserts multiple rows when check constraint occurs. Microsoft Connect Item: 811560
- Fixed an issue where Japanese Management Studio 2016 does not work completely in creating Availability Group.
- Fixed an issue where clicking query plan XML does not open the SSMS Graphical UI.
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!
- Anonymous
December 05, 2016
Is the Configuration Manager not connecting to WMI when the engine is not installed going to be fixed soon?ThanksChris - Anonymous
January 09, 2017
Do you really actively look at the connect bugs for SSMS? Many that I'm following on the connect site (and that I've commented on giving detailed explanations of the problem) go without comment from you guys for several months or even many months and years. It seems the SSMS team is disconnected/disengaged from the developer community. I certainly realize there can be hundreds/thousands of connect bugs and it's hard to respond to all of them, but that really can't be the issue here.There are some severe bugs that several people like me have contributed to regularly, but there's no MS response. The most severe one to me is where closing a tab in SSMS leaves the next visible tab showing the wrong text/code because of a redrawing/painting issue, leaving you thinking that you're working on the wrong tab!! The following connect ID's are about this same problem: 3116111, 3109897 (says 2014 but still applies to latest 16.5.1 version), 3103398, 976947.