We were at one point looking at using SSIS scale out for our environment. As it turns out, we won't be generating near enough traffic to warrant the additional horsepower, so we want to decommission the worker node. Also, we need to remove any trace of a previous master/worker environment off of our "main" server. It appears they may be some unforeseen issues with deploying certain types of packages to a server that leverages certain types of connection managers.
Specifically, we are running into issues with deploying packages that use a project level DQS connection manager. When trying to deploy a project that has packages like these, the deploy continually fails on the "Changing protection level" step. These exact same projects that fail deploy fine with no issues to our development environment. Both environments are at the same SQL Server level (14.0.3045.24). The only difference is that one is configured as a scale out master, the other isn't.
Do we need to completely reinstall SQL Server to remove those components, or can we just use Installation Center and "uncheck" scale out and it will do the rest?
And has anyone else seen anything like this ever?? I have no idea what DQS Connection managers would have to do with protection levels and scale out...
I'm at a loss on this one!
Thanks in advance
A. M. Robinson