Since SSIS does not like being merged nicely I was wondering how to have a big SSIS package split up. With the idea of having multiple devs working on this simultaneously, and a minimal chance of having merge conflicts.
In SSIS 2016 I found these options:
- package parts, but apparently they don't share connection managers. I don't want to have 100 different connection managers.
- subpackages, still this doesn't look very clean and I also wonder if this is what it is intended for. Also, the debugger goes crazy too opening the subpackages while running. Any other drawbacks I should know of?
I can't be the only person with this problem. Is there an other way to achieve this?