MicrosoftMicrosoftI must admit, it's really frustrating to see that the feature you heavily use, SSIS, isn't supported in SSMS 21, but in the same breath be told that SSMS 20 is no longer supported; in one swoop I'm now only able to use an unsupported release.
In my mind, if the SSMS 21 release is going to be incomplete, then support for the prior release, SSMS 20, shouldn't be revoked until the upgrade path is complete.
MicrosoftThom_A Thanks for your feedback. For clarification, when we state that SSMS 20 is no longer supported, it means that if you find a problem in SSMS 20 then we will fix in the current release (SSMS 21) and not back port it to a SSMS 20 release. We don't block customers from using SSMS 20 (or earlier releases) and we recognize that many customers (and companies) cannot immediately update to the newest release.
erinstellato Can you please clarify the documentation about that topic? Currently it states that no other SSMS version but the latest major version get security updates. Combined with the SSIS as preview-only and the typical "Class not registered" on connecting to older SQL Server Integration Services version, this is a disaster.
MicrosoftJensDamm When you state "Typical "Class not registered" on connecting to older SQL Server Integration Services version", I believe you're referring to the requirement that in order to connect to the legacy SSIS service, you must use the version of SSMS that aligns to the specific version of SQL Server to which you're trying to connect, as documented here: https://learn.microsoft.com/ssms/system-requirements#supported-sql-offerings. Is that correct? If so, then should there be a high-impact security vulnerability specific to SSIS for an older version of SSMS that customers use to connect to the legacy SSIS service, then we would patch that specific release of SSMS to address the security vulnerability. Please help me understand what "this is a disaster" means. Thank you.
