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

Entity relationship diagram

The final step is to draw the ERD, just like we did in Chapter 2, Entity Analysis. The understanding of ERDs you acquired in the aforementioned chapter will serve you well in understanding the results of normalizing. The key part of this step is to recognize all foreign keys. Using entity analysis, you think entities have relationships. Recognizing foreign keys means you now know that there are relationships and that you can tell the database about them later when implementing the database. You can show all columns in an ERD, or just show the tables as rectangles with just the table name written in them.

The ERD of our project administration is now as can be seen in Figure 3.16:

Figure 3.16 – ERD project administration

In Figure 3.16, the colors indicate the foreign keys and the relationships they implement. The value of drawing the ERD is twofold:

  • To get an overall picture
  • To show the necessary details
...