I rarely need to connect to SSIS in SSMS, and I do a lot of SSIS development. It would be nice to get clarification if this is a bug or will the SQL SSMS tools not "Really" be backward compatible? Then I would need both 16.5.3 and also 17.x on them and they are easily frustrated having to figure out which tool for what. ![]() Does anyone know if the plan is to not allow SSMS 17.x tools to connect to SQL 2016 Integration Services to upload packages? If it is not, I hate to move forward with 17.x tools on the developers machines. We are in the middle of planning our 2016 environment and what tools need installed on developers machines. ![]() It appears it is the same issue we have been use to where to connect to Integration Services we have to use the same version SSMS as the Integration Services version. SQL Server Management Studio 16.5.3 connects fine to 2016 Integration Services. SQL Server Management Studio 17.2 cannot connect to SQL Server 2016 Integration Services.
0 Comments
Leave a Reply. |