Deployment - SQL Server Integration Services Design Patterns - page 446

Location Notes

• Deploys through DTSInstall.exe (legacy deployment wizard), the SSIS ob-
ject model, or dtutil.exe

Package
Store (SSIS
Service)

• Provides a façade over the File System and MSDB storage locations, allow-
ing you to change the physical location of a package, yet keep the same logical
path
• Manages multiple storage locations from a single place
• Deploys through SSMS, the SSIS object model, or dtutil.exe
• Requires special DCOM permission configuration for access

Note You cannot use the Package Store interface to manage packages deployed to
the SSIS Catalog. The service is only able to interact with packages stored in MSDB
(the 2005, and 2008 deployment model), and is there to continue supporting users who
have not migrated to the new Project Deployment Model. It may be depreciated in the
future.

Conclusion

The deployment process for SSIS packages was greatly simplified in SQL Server 2012.
Although the deployment model used in SQL Server 2005 and 2008 (now called the
Package Deployment Model) is still fully supported, moving to the new Project
Deployment Model is highly recommended for new data integration projects. SSIS
provides a number of ways to deploy to the SSIS Catalog, providing the flexibility you
need to fit the deployment process into your environment.