We've recently upgraded to SQL2014 and we're keen to move over to Project Deployment Model for our SSIS Packages.
One thing which is slightly off-putting is that you have to deploy all packages in a project together, rather than being able to deploy a single package. We have several hundred packages, and the idea of deploying them all just to make a small change seems a bit overkill. So we've decided to split them into multiple projects based on their functionality. This means we can only deploy a small number of related packages with each deployment.
This is working well, with one exception. Opening up the Solution is a giant pain in the ***, as each of our projects is password protected. This means we get prompted for the password for every project in the solution, each time the Solution loads. This seems like a massive usability oversight, does anyone have any solution to it?
It's simply not sustainable to be typing in dozens of passwords each time we open the Solution, which leaves us with three options:
1. Go back to Package Deployment Model, and lose all the benefits of SSISDB and Project Parameters etc.
2. Put everything in one Project, and end up having to deploy hundreds of packages each time
3. Put everything in separate solutions, meaning we have to open multiple instances of Visual Studio.
None of those seem particularly good, so I'm hoping that someone has a solution!