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
Data Modeling for Azure Data Services

You're reading from   Data Modeling for Azure Data Services Implement professional data design and structures in Azure

Arrow left icon
Product type Paperback
Published in Jul 2021
Publisher Packt
ISBN-13 9781801077347
Length 428 pages
Edition 1st Edition
Languages
Tools
Concepts
Arrow right icon
Author (1):
Arrow left icon
Peter ter Braake Peter ter Braake
Author Profile Icon Peter ter Braake
Peter ter Braake
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Preface 1. Section 1 – Operational/OLTP Databases
2. Chapter 1: Introduction to Databases FREE CHAPTER 3. Chapter 2: Entity Analysis 4. Chapter 3: Normalizing Data 5. Chapter 4: Provisioning and Implementing an Azure SQL DB 6. Chapter 5: Designing a NoSQL Database 7. Chapter 6: Provisioning and Implementing an Azure Cosmos DB Database 8. Section 2 – Analytics with a Data Lake and Data Warehouse
9. Chapter 7: Dimensional Modeling 10. Chapter 8: Provisioning and Implementing an Azure Synapse SQL Pool 11. Chapter 9: Data Vault Modeling 12. Chapter 10: Designing and Implementing a Data Lake Using Azure Storage 13. Section 3 – ETL with Azure Data Factory
14. Chapter 11: Implementing ETL Using Azure Data Factory 15. Other Books You May Enjoy

Creating multiple storage accounts

You can provision as many storage accounts as you like. There are four high-level considerations when it comes to choosing how many storage accounts you need:

  • DTAP
  • Data diversity
  • Cost sensitivity
  • Management overhead

Let's look at each of them in a little more detail.

Considering DTAP

DTAP stands for development, testing, acceptance, and production. Each stands for a separate environment used in a separate stage in the creation of, and working with, a data lake. You probably need to create some code to move data from the source systems into the data lake and then through the different data lake zones. This is a work in progress that should be separated from business processes working with data already in the data lake. You will most likely want to have small test datasets to create the logic and workflow to save development time.

After new software is written, it must be tested. You may have separate datasets...

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