Book Image

Microsoft SQL Server 2012 Integration Services: An Expert Cookbook

Book Image

Microsoft SQL Server 2012 Integration Services: An Expert Cookbook

Overview of this book

SQL Server Integration Services (SSIS) is a leading tool in the data warehouse industry - used for performing extraction, transformation, and load operations. This book is aligned with the most common methodology associated with SSIS known as Extract Transform and Load (ETL); ETL is responsible for the extraction of data from several sources, their cleansing, customization, and loading into a central repository normally called Data Warehouse or Data Mart.Microsoft SQL Server 2012 Integration Services: An Expert Cookbook covers all the aspects of SSIS 2012 with lots of real-world scenarios to help readers understand usages of SSIS in every environment. Written by two SQL Server MVPs who have in-depth knowledge of SSIS having worked with it for many years.This book starts by creating simple data transfer packages with wizards and illustrates how to create more complex data transfer packages, troubleshoot packages, make robust SSIS packages, and how to boost the performance of data consolidation with SSIS. It then covers data flow transformations and advanced transformations for data cleansing, fuzzy and term extraction in detail. The book then dives deep into making a dynamic package with the help of expressions and variables, and performance tuning and consideration.
Table of Contents (23 chapters)
Microsoft SQL Server 2012 Integration Services: An Expert Cookbook
Credits
Foreword
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

The Package Deployment Model, Using SSDT to deploy package


There is a legacy Deployment Model, which is the Package Deployment Model. The Package Deployment Model is completely based on packages instead of projects. So each package deploys independently and there is no advantage to having all packages in one project for deployment purposes.

Package Deployment Model was the only deployment model for SSIS 2005 and 2008. As we discussed earlier, the Project Deployment Model is much better for a project environment, but as we are working legacy models with SSDT, we should know how to deploy in legacy model.

In this recipe, first we convert a project to Package Deployment Model, and then we deploy the child package with SSDT.

Getting ready

Convert the project to the Package Deployment Model:

  1. Create a project and name it R03_Package Deployment Model.

  2. Remove the package.dtsx file and copy P02_Child.dtsx from the R01_Deployment from SSDT project to this one.

  3. Right-click on the project name in Solution...