Blog Post

SQL Server Blog
4 MIN READ

SQL Server Management Studio (SSMS) 19.1 and Recent Changes, Part 2

erinstellato's avatar
erinstellato
Icon for Microsoft rankMicrosoft
Jun 12, 2023
This is the second post in a series discussing changes between SSMS 18.12.1 and SSMS 19, and new functionality in SSMS 19.1.  You can view the first post covering Microsoft.Data.Sqlclient and MSAL he...
Screenshot of SQL Server version displayed in Object Explorer
Updated Feb 03, 2025
Version 2.0
sqlserver2022
sqltools
Pablo_Lerner's avatar
Pablo_Lerner
Brass Contributor
Jun 16, 2023

Hi, erinstellato, thanks for the reply. A few things that come to my mind right now, about SSMS:

  • get database connections to (always) remember passwords. It still does not very often.
  • get the object explorer to order the object tree by schema.
  • get SQL Agent jobs to somehow show their categories. These categories are kind of hidden and not easily visible.
  • get SQL Agent schedules to be more visible. They are kind of hidden and not easily visible. Most people that I know think all schedules are independent for each job and don't know they can be shared.
  • show the IO and TIME statistics in a way to make them easy to understand (SET STATISTICS TIME/IO).
  • Add visibility and some administration capabilities for all the Service Broker functionality. (or just declare it deprecated, I guess? I don't really know, does anyone use it?)
  • add the possibility to get into source control the objects inside a database directly, without having to use external scripts. Some Add Ins allow for this (Red Gate, dbForge, ApexSQL, etc). And allow centralized source control software. GIT does not work for me since we are a team of 10 developers working on the same development database and we need everyone to see the same in the database and in the source control software.