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

Control Flow Task and variables considerations for boosting performance


Several considerations can be applied to get even more performance from SSIS packages. To take control and make it possible, firstly you need to know the present performance in order to monitor and evaluate every step for boosting the performance. One important consideration when implementing SSIS projects is to avoid doing all the work in just one or a few packages. Splitting the work into several packages gives more flexibility for future troubleshooting and reduces risk when a change must be applied. Other considerations can be:

  • Design the Control Flow in order to have tasks executing in parallel. If some of the tasks have precedent constraints and you cannot execute in parallel, make use of the the Sequence Container. In this way it is possible to execute some tasks in parallel (inside the container) and have others executed after the container's execution (the container status can be Completed, Success, or Failure...