Deployment - SQL Server Integration Services Design Patterns - page 433

CHAPTER 18
Deployment
Great strides were made towards simplifying the deployment process for Integration
Services projects in SQL Server 2012. Projects within Visual Studio can now target two
different deployment models - the Package Deployment Model, which is similar to what
was used in previous versions of the product, and the Project Deployment Model, which
was designed for the new SSIS Catalog.
This chapter will focus on patterns associated with the new Project Deployment
Model and server based deployment. While the Project Model and SSIS Catalog are the
recommended way to do deployment, organizations upgrading from previous versions
may already have package execution frameworks that rely on file system based deploy-
ment.
Note SSIS package deployment was not changed between SQL Server 2012 and SQL
Server 2014.
Project Deployment Model
The new Project Model is the default target when creating SSIS projects in SQL Server
2014. With this model, packages and other project items such as Shared Connection
Managers are bundled into a single file with an .ispac extension during the project's
Build phase. This file can then be deployed to the SSIS Catalog using the Deployment
Wizard, or executed directly using dtexec.exe.