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

Key-value databases

With Azure Table storage (or just Azure tables), Microsoft also offers a key-value database. The Table API of Cosmos DB lets you write code against Cosmos DB as if it were a key-value database. This should facilitate the migration of Azure tables implementations to Cosmos DB. Azure tables have less functionality than Cosmos DB but are also cheaper. It is worth looking into key-value databases.

A key-value database stores data in values. Values can easily be retrieved using a key. It is comparable to a table with just two columns, a key column and a value column. The key is likely informative data by itself. The value is likely compound information.

Suppose you create an account on a website based on a key-value database. Your email address is used as the username. Your email address would be the key of the underlying key-value database. Using a hashing algorithm, the key determines the cluster node to store the data on. The value stores all the information...

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