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

Using a Kimball data warehouse versus data marts

The starting point of creating a star schema is choosing a process to model. One star model describes one process. A business is always more than a single process. In the theory of Ralph Kimball, a data warehouse is the collection of all star schemas that together describe the entire organization.

There will always be overlap between the individual star schemas you create to model the individual processes. The processes are not completely independent of each other. The sales department sells products that the purchasing department buys. They work with the same products. So, the star schema describing the sales process will have the dimProduct and dimDate dimensions in common with the star for purchasing. They will have different dimensions as well. The star schema for purchasing might have a dimension for suppliers, whereas the sales start schema probably has a dimension for customers.

When you design the dimProduct dimension table...

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