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
The brand new PASS SQL Server User Group in Daytona Beach let me present at their very first meeting July 13th. Thanks to Brook Ranne and Jim McAleer for inviting me. I debuted a presentation on the changes forthcoming in SSIS with Denali. The slides are available here. If you are in the Daytona Beach area please check this group out!
I also just wanted to share some exciting news for me. I submitted three sessions for this year’s PASS Summit. When the schedule came out, none of them made the final selection. However, this week I found out there still might be hope. PASS has put together a Community Choice Ballot of 20 sessions for you the community to vote on, and one of mine (SQL Smackdown with Aaron Nelson) made the ballot! There are five available slots we are competing for. As I always say, I would love your vote, but regardless of whom you vote for, you should let your choice be known, as there are amazing sessions on the ballot! Voting ends July 20th, so hurry! And thank you readers for your support this year, without you I’m sure I wouldn’t be on the ballot at all.
Check out the Community Choice Ballot here.