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

Summary

We started this chapter by explaining the most common data types in SQL Server. Choosing the right data types is an important step in the design process. Data types determine both the efficiency and functionality of the database.

We then provisioned a database in Azure SQL Database. Choosing the right performance tier is important. If you under-provision a database, you will experience bad performance. If you over-provision a database, you are wasting money. Because the way a database is used over time may change, you need to monitor the database and rescale whenever necessary. It is important to note that a well-designed database requires fewer resources to handle the same workload as a badly designed database.

After provisioning a database, you need to create tables. This is where you implement the design you made.

Now that you have learned a lot about SQL databases, it is time to look at designing a NoSQL database in the next chapter.