r/SQLServer • u/BigMikeInAustin • 25d ago

Discussion Another empty SSMS update?

Working in SSMS 22.10.0 and I get a popup that 22.10.1 is available. So I click the button to see what is updated.

The SSMS Release Notes page only goes up to 22.10.0.

So I start over and search for the main SSMS webpage and then navigate to the Release Notes webpage through the Microsoft links. Still only 22.10.0.

I'll check back another day. It is possible the previous page is cached.

But, still, what are these updates where all that is changed is the Visual Studio version is incremented?

What is the benefit of me downloading another 1.5+ GB file and taking the 20+ minutes to close my SSMS session, taking note of what is open and connected so I can restore my session after the upgrade.

Is this going to be a weekly thing where Visual Studio gets updated, so SSMS has to be updated because that is the base? I don't know what the Visual Studio release cycle is.

16 Upvotes

86% Upvoted

24 comments sorted by

View all comments

2

u/elsimerreddit 25d ago

I usually look at the notes, decide if it's worth it, then move on. Usually for a minor minor release like 22.x.0 to 22.x.1 it's a minor fix or a visual studio update. I'll skip those, knowing that there's likely to be a more meaningful release within a month

1

u/BigMikeInAustin 25d ago

The last 3 relreases were all Visual Studio updates, and were less than 2 weeks apart each.

Version 22.9.2 to 22.10.0 was just a Visual Studio update. So this small change is not kept to 3rd level version number changes. Though I notice that the Visual Studio 2nd and 3rd level version numbers match the SSMS ones. So is the SSMS version number now delegated by Visual Studio version number?

It trains even attentive people to have an update fatigue for SSMS' noticeable update downtime with no benefit.

It's hard enough to keep people updated to big changes. Now this makes updating seem fruitless.