Book Image

Data Modeling for Azure Data Services

By : Peter ter Braake
Book Image

Data Modeling for Azure Data Services

By: Peter ter Braake

Overview of this book

Data is at the heart of all applications and forms the foundation of modern data-driven businesses. With the multitude of data-related use cases and the availability of different data services, choosing the right service and implementing the right design becomes paramount to successful implementation. Data Modeling for Azure Data Services starts with an introduction to databases, entity analysis, and normalizing data. The book then shows you how to design a NoSQL database for optimal performance and scalability and covers how to provision and implement Azure SQL DB, Azure Cosmos DB, and Azure Synapse SQL Pool. As you progress through the chapters, you'll learn about data analytics, Azure Data Lake, and Azure SQL Data Warehouse and explore dimensional modeling, data vault modeling, along with designing and implementing a Data Lake using Azure Storage. You'll also learn how to implement ETL with Azure Data Factory. By the end of this book, you'll have a solid understanding of which Azure data services are the best fit for your model and how to implement the best design for your solution.
Table of Contents (16 chapters)
1
Section 1 – Operational/OLTP Databases
8
Section 2 – Analytics with a Data Lake and Data Warehouse
13
Section 3 – ETL with Azure Data Factory

Relationships

ERDs are not solely about entities but are also about their relationships. Let's return to the example where we sell products to customers. Do Product and Customer have a relationship?

Figure 2.5 – Is there a relationship between Product and Customer?

At first glance, you might think Product and Customer do have a relationship. A customer buys your products. Nouns are often good indicators of entities, while verbs are indicators of relationships. "Buys" seems to suggest there is a relationship. However, we need to look closer. What if a customer buys a product and next week they come back to buy the same product again? We probably want to keep records of both events, both sales transactions, individually. They might fall in different calendar quarters, meaning there is a difference for you in terms of payments of VAT to the government.

There is a third entity: Sales transaction or Order. Every time you log in to an online...