I have a clean installation of SQL Server 2016 Enterprise Edition SP1 on a fresh Win Server 2012R2 Standard Edition. Added all the features and for some reasons I am not able to login to the SSIS service installed using SSMS. SSMS is also a separate installation (latest version ssms 16.5.3). I am not able to see the SSIS server installed even though I can clearly start and stop it using the configuration manager. Some were saying to run the ssms as administrator and that didnt help. Your help is appreciated. See images for details.
This is documented as a defect, but it isn't. Use SSMS 16.x for SQL 2016 and for SQL 2017 use SSMS 17.x. Also note that 16.x will not work with SQL 2014, as this is by design. Setting up and using SSISDB is what Microsoft wants; look for the notes in the box at the provided link.
This information came from our Microsoft SQL representative, though its posted as well. Click here to download 16.5.3 from Microsoft.
The SSIS Service is not used in SQL 2016
It's a legacy service, only needed in a very specific case - if you have older versions of packages that you haven't upgraded, that you need to store in MSDB.
It is replaced by the SSISDB and SSIS catalog
Why do you think you need to connect to it?
See here for more info:
https://auntkathisql.com/2015/01/15/what-is-the-ssis-catalog/
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With