We’ve deployed the project to a folder in SSIS Catalog, now let’s create Environments and Environment Variables inside the SSIS Catalog:
Lesson Two. Deploying Projects in SSIS 2012 (Today’s class is longer than I expected, we’ll take a break and finish tomorrow.)
PreRequisite: Lesson One
By the end of this part of the lesson you should understand the following processes/terms.
- Building SSIS Projects
- Ispac files
- The SSIS Catalog
- Deploying ispac files
By the end of the second half of the lesson, the following will be covered:
- SSIS Catalog Environments
- SSIS Catalog Environment Variables.
- SSIS Executions
- Building Agent jobs with SSIS Catalog projects.
So you’ve got your Project with a Parent package. (by the way, you should designate Parent Packages as Entry Point packages inside a project by right clicking them and selecting “Entry Point Package”). You’ve got some child packages. You’ve got some variables. You’ve got project level parameters for values which should be available to all packages inside a project (like say, a directory for importing/exporting files, a client to process, a business unit to process, etc. ) and you’ve got package parameters for values which need to be passed from parent packages to child packages. You’re ready to Build, Deploy and Execute in SSIS 2012 utilizing all of its new toys features.
Oooo shiny new SSIS Project—Ready for Deployment
Lesson One, where I introduce tons of prerequisite new concepts in preparation for Deploying and Executing in Lesson Two. The main concepts and terms covered in this lesson are:
- Project Deployment Model
- Legacy Deployment Model
- Project Reference reference type –Execute Package Task
- Ispac files
- Parameters, subdivided into the two following subtypes:
- Project Parameters
- Package Parameters
It will help if you are familiar with the following concepts inside SSIS (pre 2012 versions) before attempting this course 😉
- Execute SQL Task
- Execute Package Task
- Connection Managers
- Parent/Child packages
SSIS in 2012 brings a great number of significant changes. It is the first version since its initial release with SQL Server 2005 to look significantly different. There is a more modern look and feel to be sure. However, the really big change to SSIS in 2012 is in the way in which it is deployed. There is a new method of deployment called “Project Deployment”, which has as much to do with how and where a package is deployed as it does with how a package is bundled during development. Let me go back in time a bit and explain. Continue reading SQL University– SSIS 2012: Deploying Projects –Lesson One