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

Entities

According to Merriam-Webster, an entity is "something that has separate and distinct existence and objective or conceptual reality." A more practical description would be something that you want to store characteristics about. When you sell products to customers, you need to keep track of certain characteristics or properties of those products. At a minimum, you need to know the price that the product sells for. So here, the product is an entity and the price is a characteristic of the entity. Attribute is another often-used word for a characteristic or property.

Entities translate easily into tables. For each entity that plays a role in a process, we create a separate table in the database. Each characteristic or attribute that you need to keep track of will become a column in the table.

Using the term entity is not completely accurate (but it is a term in everyday use). Most of the time, we mean entity type when we say entity. An entity type is a generic...