Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
ETL with Azure Cookbook

You're reading from   ETL with Azure Cookbook Practical recipes for building modern ETL solutions to load and transform data from any source

Arrow left icon
Product type Paperback
Published in Sep 2020
Publisher Packt
ISBN-13 9781800203310
Length 446 pages
Edition 1st Edition
Languages
Tools
Concepts
Arrow right icon
Authors (3):
Arrow left icon
Christian Cote Christian Cote
Author Profile Icon Christian Cote
Christian Cote
Matija Lah Matija Lah
Author Profile Icon Matija Lah
Matija Lah
Madina Saitakhmetova Madina Saitakhmetova
Author Profile Icon Madina Saitakhmetova
Madina Saitakhmetova
Arrow right icon
View More author details
Toc

Table of Contents (12) Chapters Close

Preface 1. Chapter 1: Getting Started with Azure and SSIS 2019 2. Chapter 2: Introducing ETL FREE CHAPTER 3. Chapter 3: Creating and Using SQL Server 2019 Big Data Clusters 4. Chapter 4: Azure Data Integration 5. Chapter 5: Extending SSIS with Custom Tasks and Transformations 6. Chapter 6: Azure Data Factory 7. Chapter 7: Azure Databricks 8. Chapter 8: SSIS Migration Strategies 9. Chapter 9: Profiling data in Azure 10. Chapter 10: Manage SSIS and Azure Data Factory with Biml 11. Other Books You May Enjoy

Generating a mass change to stored procedures

If we want to automatically generate the sample SSIS package for the WideWorldImporters solution, as we intended to do in the beginning, we need to work on some prerequisites. These prerequisites are so interesting and challenging that it is best to dedicate a separate recipe to them. The SSIS package from the sample WideWorldImporters solution uses Get stored procedures in the Data Flow Task OLE DB Source to retrieve data from the source. In the original package, the EXECUTE statement calling each Get stored procedure uses the RESULT SET clause to specify data types and column names for the return result set. This is necessary for SSIS to work correctly because all Get stored procedures use temp tables and since temp tables are resolved at runtime, SSIS is unable to retrieve metadata for every output column of the result dataset.

The use of temp tables is a challenge for Biml as well, and in addition to the RESULT SET clause, we need...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image