At my current work place we use SQL Server 2008R2 and have implemented something we call an "SSIS Library".
It is essentially a set of SSIS packages that are utilized across multiple projects/solutions.
The idea is to have shared code across multiple solutions - just like you have libraries in other programming languages that you just import and use.
We've created a set of SSIS packages (Library) and a set of Wrapper packages. The wrapper packages would get imported into a specific client project, get parameters and feed them to centrally located Library packages.
It has been working nicely, until we started thinking about migration to SQL Server 2012.
In SQL Server 2012 the new project level deployment model only allows one to use/execute packages from other packages within the same project - not across projects. This introduces a problem as we will not be able to call a Library solution from a Wrapper solution from the main Client solution (which is the current hierarchy of package execution).
Has anyone stumbled on the same problem and found a resolution (other than using the legacy model that might not exist in 2014)?
Do you know if "external referencing" has something to do with using the old package level deployment model or are two concepts independent?
Nope external reference comes in Package deployment model. You will reference packages outside of current project through external references. But there are few restrictions on that. I've just heard of it but havent had a chance to use it so far