SQL Server Integration Services 2012 supports two deployment models: project and package. The well-known package model is now a legacy model and we are not going to cover this here. There are many advantages to using the new project model that you will benefit from, so we will explore these instead.
As you have probably already guessed, when deploying using the project model all packages are deployed together, whereas the package model deploys just a single package. The project deployment deploys to the SSISDB catalog that we created earlier and which sits under the Integration Services Catalogs folder in the Object Explorer pane in Management Studio. Don't let the name of this folder lead you astray—you can only have one SSISDB catalog per server.
Let us look at some of the advantages and disadvantages of using project rather than package deploymen:
The project, containing all the packages and parameters, is built to a single
.ispac
file. Again this is easier to manage...