次の方法で共有

Announcing SQL Server Management Studio - January 2016 Release

  • [アーティクル]

Today, we are happy to announce the latest preview of SQL Server Management Studio (SSMS). This release includes all updates included in last year’s December release, and features numerous bug fixes in Always Encrypted dialogs, Extended Events sessions, and many more.

Get it here: Download SSMS January 2016 Preview

  • The version number for the latest preview is 13.0.1000.281

New in this release

  1. Bug fix in SSMS to allow the deletion of Extended Events (XEvent) sessions.
  2. Fix for Microsoft Connect bug #1609719: to open properties dialog for a SQL Server 2014 availability group.
  3. Fix for Microsoft Connect bug #2029135: to enable the ability to add an Azure replica to an Availability Group.
  4. Fix for Microsoft Connect bug #2080209: to open properties dialog for SQL Server 2014 databases.
  5. Fix for Microsoft Connect bug #2103116: to remove duplicate columns that appear for each table when connected to an Azure SQL database.

Please visit the SSMS download page for additional details including Microsoft connect IDs for issues that were fixed.

Known issues

  • Distributed replay is known to not work with the SSMS January 2016 release. We are working on a fix for this issue which will be available in the next SSMS release.

The full list of known issues is available in Release notes available here.

Contact us

If you have any questions or feedback, please visit our forum or Microsoft Connect page. We are fully committed to improve the SSMS experience and look forward to hearing from you!

Comments

  • Anonymous
    February 23, 2016
    I installed this on a machine with SQL Server 2012 SSMS version 11.0.6020.0. I have a fairly large hierarchy of managed servers that I created with a powershell script using the SQLPS technique of new-item $Name -itemtype registration -Value "server=$Name;integrated security=true" The servers I have in the 2012 SSMS don't show up as registered servers in this 2016 preview version. Shouldn't this pick up the entries since they are there in the SQLSERVER: "drive"?