Book Image

ETL with Azure Cookbook

By : Christian Cote, Matija Lah, Madina Saitakhmetova
Book Image

ETL with Azure Cookbook

By: Christian Cote, Matija Lah, Madina Saitakhmetova

Overview of this book

ETL is one of the most common and tedious procedures for moving and processing data from one database to another. With the help of this book, you will be able to speed up the process by designing effective ETL solutions using the Azure services available for handling and transforming any data to suit your requirements. With this cookbook, you’ll become well versed in all the features of SQL Server Integration Services (SSIS) to perform data migration and ETL tasks that integrate with Azure. You’ll learn how to transform data in Azure and understand how legacy systems perform ETL on-premises using SSIS. Later chapters will get you up to speed with connecting and retrieving data from SQL Server 2019 Big Data Clusters, and even show you how to extend and customize the SSIS toolbox using custom-developed tasks and transforms. This ETL book also contains practical recipes for moving and transforming data with Azure services, such as Data Factory and Azure Databricks, and lets you explore various options for migrating SSIS packages to Azure. Toward the end, you’ll find out how to profile data in the cloud and automate service creation with Business Intelligence Markup Language (BIML). By the end of this book, you’ll have developed the skills you need to create and automate ETL solutions on-premises as well as in Azure.
Table of Contents (12 chapters)

Upgrading a Custom Data Flow Component

When you determine that a custom component that might have already been deployed to production use needs to be modified – for instance, to implement a bug fix, to add an improvement, or simply to extend its capabilities – you can take advantage of a built-in feature of the PipelineComponent class to automate the upgrade.

Tip

In general, all the changes needed by the upgrade should be delivered without the need for user intervention – for instance, if the new version uses properties that were not available in the previous version(s), then default values should be provided as well.

After the new version of the component has been deployed to the target environment, the upgrade is performed automatically:

  • At design time when the package that implements the component is opened in SSDT
  • At runtime when the package that implements the component is executed

    Important note

    If the upgrade cannot be completed successfully...