MicrosoftMicrosofterinstellato With Disaster I mean corporate reaction on setting all older SSMS versions SEoL (Security EoL). Microsoft forces us to keep the old SSMS version, as you recognized, but in the same time, the automated vulnerability scans find the old SSMS and guess the reaction: it will be uninstalled and replaced by the only supported version of SSMS v21 (at the current date). This causes issues because we cannot access the SSIS instance anymore...
Please reverse the SEoL for older SSMS versions in the official documentation or add support for legacy SSIS connections in the latest SSMS.
MicrosoftJensDamm What does "corporate reaction" mean? And what automated vulnerability scans are you running and how do they determine that an older SSMS is vulnerable?
"Corporate reaction" -> If an unsupported software is detected, they will react on it. The DBA team deinstalls the older SSMS and will now install only the latest version, as they are not allowed to use software out of support without going through an exception process.
As you wrote:
With the release of SSMS 21, previous versions of SSMS will no longer receive support, as per our https://learn.microsoft.com/ssms/support-policy. We strongly recommend upgrading to SSMS 21 to access the latest features, security updates, and critical fixes.
MicrosoftJensDamm Our recommendation would be that the DBA team file an exception for the version of SSMS that's needed to support the organization's legacy SSIS connections. We have no plans to change the support policy for SSMS. SSIS introduced use of the SSIS catalog (SSISDB) in SQL Server 2012, and I recognize that legacy integrations can time to modernize, but that's a worthwhile investment to make before an organization may be forced to do so.
erinstellato We would need to wait or the vendor (a Microsoft partner) to update their software to support SSISDB (or migrate away from SSIS)...
Just to be sure, because the support policy is hard to read/understand or is conflicting with the information from that blog entry:
There will be no security updates for earlier SSMS versions (before v21) anymore?
And a feature which is existing in the supported SQL Server version is basically not fully working anymore because the software to maintain it, is not supported anymore?
To Erin's defence, if you can't use unsupported software, would it not make sense to therefore "update" to SSISDB? The legacy deployment method has been deprecated for some time, and SSISDB isn't SSMS edition locked. Isn't the legacy deployment method going to be removed in SQL Server 2025 as well?
