Why this has been happening Due to some architectural changes to SSMS that were introduced from the v21 release onwards, we've seen a significantly higher volume of dependency changes than ever before. Because our tools run as plugins inside SSMS rather than as separate processes, every dependency update means we need to make sure our products still support it. That's made keeping pace with SSMS releases considerably more challenging than it used to be. What we've already changed, and what's next We want to be transparent that we've been actively working on this, and a number of improvements are already in place:
We've changed the default upgrade mechanism so SQL Prompt now updates the whole of SQL Toolbelt Essentials rather than individual products. A lot of the crashes were caused by one TBE product being updated while others weren't, leaving users on a mixed and unsupported set of versions, which matches what some of you found above with old or unused Redgate tools (like SQL Dependency Tracker) causing the crash. This change has meaningfully reduced the frequency of issues.
We now get early access to SSMS release candidates ahead of the monthly public release, which lets us test and get fixes out before it lands for everyone. This has proven largely reliable, though it doesn't fully eliminate risk since last minute changes can still happen. We'll keep investing in this regression testing.
We believe the last few SSMS releases haven't required any hotfixes on our side. If your team has kept seeing problems on the latest versions of both SSMS and SQL Toolbelt Essentials, we'd like to know, since it may point to something specific to your environment that we're not aware of.
We do acknowledge the SSMS 22.6 release caught a library issue in our licensing code, which we're sorry for. That one got through our testing process.
We're also looking at how to communicate compatibility better ahead of releases, including showing verified compatible SSMS minor versions on our docs site. Not in place yet, but it's something we're committed to.
/ comments
Official comment
- Community
- SQL Prompt
- SSMS 22.6.0
Why this has been happeningDue to some architectural changes to SSMS that were introduced from the v21 release onwards, we've seen a significantly higher volume of dependency changes than ever befo...
0 votes
