Erin Stellato has a two-parter around SSMS 19.1. The first includes a small but important change:
In SSMS 19.1, the default value for Use system default web browser was changed to True. This only applies to new installations; anyone upgrading from an earlier version of SSMS 19 will need to change the option to True manually.
This means that, for new installations, clicking on a link in SSMS will no longer open in the built-in SSMS browser, which doesn’t work for a lot of newer sites.
Part 2 picks up with some additional changes:
We have heard complaints, for months, about the startup time for SSMS. Between 18.12.1 and 19.0 we made a few changes, and in 19.1 we delayed initializing the output window to also reduce startup time. Some of you noticed! Glenn Berry completed a round of testing and documented findings in his SSMS 19.1 Performance Improvements blog post. We are hoping to also gain improvement when we get to SSMS 20, so know that our work is not yet done.
Click through for the full set of chnages.
SSMS 20:
64-bit app
Create same Extension mechanism as ADS and Visual Studio Code
Stop hanging on cancelled queries where the SPID has already spun down
Azure to On-Prem Upsizers for those who value performance over convenience
Prefacing this with my standard “I don’t know nothin’ ’bout nothin’!” disclaimer regarding what the future holds:
– I think we could see a move to a 64-bit app, given that Visual Studio finally made the jump. Will it be in time for SSMS 20? No idea, but fingers crossed.
– I expect we will *not* get the same extensions mechanism as is available for Azure Data Studio. VS Code was intended from the beginning to handle extensions easily, whereas the VS shell simply wasn’t.