Upgrading to the Project Deployment Model
In SSIS 2012, the project deployment model has become the new standard for how packages are created, configured, and deployed. Any new packages that are developed are automatically set up to use the project deployment model.
Having this new deployment model means several things for you, especially if you developed SSIS packages in previous versions of SQL Server. For example, these features, which you may have used previously, are no longer available in the project deployment model:
- Data sources
- Package deployment
Although the features have been removed in the project deployment model, they are easily replaced with new tools. Following are some of the major features that are either new or have been changed in the project deployment model:
- Project connection managers (discussed in Lesson 6)
- Project deployment (discussed in Lesson 53)
- Project parameters (discussed in Lesson 33)
- Environments and environment variables (discussed in Lesson 54)
As you can see, much of what you can do when developing is focused more on the project than the package, as it was in the past. This may change how you organize your packages because, as “project deployment” implies, you will now be deploying entire projects and not just individual packages. So if you put all your packages into a single project, regardless of what part of the business they affect, they will all have to go into the same deployment path with the new model.