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

Using expressions in Control Flow


Expressions provide a level of dynamism in Control Flow. Working with a Control Flow task can be much more robust when properties of the task can be set dynamically instead of having static values.

Prior to SSIS 2012, you could assign the result of an expression to a variable (writing the expression in the variable's expression property and setting the EvaluateAsExpression property of the variable to true), but problem with this method is that the value of the variable will be resolved whenever you refer the variable. For example, assume that you have a User::StartTime variable which gets the current time with the GetDate() expression function, at the end of package you want to use the User::StartTime variable to fetch start time of the package and do some calculations, but you will get the current time! This is because the expression will resolve at the time of referring to the variable. So there is a need to specify a step or it makes sense better to say...