Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
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

Product type Book
Published in Jul 2021
Publisher Packt
ISBN-13 9781801077347
Pages 428 pages
Edition 1st Edition
Languages
Concepts
Author (1):
Peter ter Braake Peter ter Braake
Profile icon Peter ter Braake
Toc

Table of Contents (16) Chapters close

Preface 1. Section 1 – Operational/OLTP Databases
2. Chapter 1: Introduction to Databases 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

Designing dimensions

The first thing to look at is the primary key to use for a dimension table.

Defining the primary key of a dimension table

To get straight to the point: we always use surrogate keys for dimension tables. In Chapter 1, Introduction to Databases, we discussed logical versus surrogate keys. We will not repeat the discussion here. The best practice is to use surrogate keys for dimension tables.

In a star schema database model, using an efficient primary key is even more important than in a normalized OLTP database. In earlier examples, it became clear that fact tables might become really big in terms of the number of rows they store. Suppose you have a fact table with seven dimensions that has 1 billion rows. The difference between using keys that are 4 bytes in size and keys that are 8 bytes in size is 7 x 4 x 1,000,000,000, which is 28 GB. Some people might argue that today 28 GB is not really something to consider. But you might have a lot more rows than...

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 ₹800/month. Cancel anytime