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
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

Creating a Databricks workspace

A Databricks workspace is an environment that contains Databricks assets such as the following:

  • Notebooks: A notebook is an interface that contains a series of runnable commands. It's a placeholder for code, visualizations, and narrative text.
  • Libraries: Can be third-party or locally based. They contain code that can be used in notebooks.
  • Experiments: Used primarily by machine learning, they allow the visualization of an MLflow run.
  • Clusters: Virtual machines in Azure that act as a compute service. They execute the code we write in notebooks.
  • Jobs: A job is used to run Databricks commands without using the notebook UI. A job is called via a scheduler or data factory.

Now that we have a better idea of the Databricks components, let's dig into it.

Getting ready

If you are using a trial Azure subscription, you will need to upgrade it to a Pay-As-You-Go subscription. Azure Databricks requires eight cores of...

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