This post has been republished via RSS; it originally appeared at: Microsoft Tech Community - Latest Blogs - .
Introduction:
SQL Server Management Studio (SSMS) 19.1 has introduced a range of updates and changes, enhancing its database management capabilities. This article provides a summary of these changes, offering insights into how they impact the functionality and user experience of SSMS.
1. Driver Updates and Configuration Changes:
SSMS 19.1 features a significant shift from System.Data.Sqlclient (SDS) to Microsoft.Data.Sqlclient (MDS), impacting how SQL Server connections are managed. This change includes validation of certificates, a new feature in MDS 3.x not present in SDS 3.x. For more details, see the full article.
2. Authentication Library Transition:
The migration from Azure Active Directory Authentication Library (ADAL) to Microsoft Authentication Library (MSAL) is another critical update. This transition responds to the end of support and development for ADAL, with MSAL offering updated capabilities aligned with the Microsoft identity platform endpoint. For further information, refer to the Microsoft Tech Community article.
3. SQL Vulnerability Assessment Removal:
The SQL Vulnerability Assessment feature has been removed from SSMS 19.1 and incorporated into Microsoft Defender for SQL. This change aims to provide real-time updates and consistent vulnerability scanning across cloud and on-premises resources. Detailed information can be found in the Part 2 of the SSMS 19.1 changes series.
4. Startup Time Improvements:
Efforts to reduce the startup time of SSMS have been made, including delaying the output window's initialization. These improvements are part of ongoing enhancements to optimize the tool's performance. For more insights, check the detailed blog post.
5. "Can't Reach This Page" Error:
A common issue in SSMS 19.1, especially in restricted network environments, is the "Can't reach this page" error when using Microsoft Entra authentication. This problem stems from the default browser setting change in SSMS 19.1. Solutions and explanations for this issue are provided in the dedicated blog post.
URLs: