Hi, I have ported my SSIS framework app to 2012 but I've hit a problem.
I have organised my packages into projects within my solution, and I have a a control package which executes these in the right order, manages dependencies, etc. Simple enough.
Or so I thought, it turns out that in the new deployment model you can only use the "Execute Package Task" on packages within your project and not across the solution.
The options that I can think of:
- Put all packages in one project. As all packages must sit under the default "SSIS Packages" folder (afaik) and I have hundreds of packages loading from many source systems this is going to be messy. I don't really want to work with a big list that I have to scroll through.
- Switch to the file system. Seems a likely option right now. Big shame as I am really liking the new way of doing things, I want to use catalogs.
- Call child packages through SQL. This seems problematic, Ive read about issues with passing params, managing async runs, bubbling up errors, etc. This just seems like a whole load of hassle.
- Something else?
Has anyone else faced this problem and if so, what have you done?
Cheers.