This chapter covers Azure SQL Database, Azure's managed relational database service. AZ-900 tests this under objective 2.4, and it's a common example when the exam discusses structured, relational data storage.
Jump to a section
A simple way to picture Azure SQL Database
Running your own database on a server is like operating your own records office — you hire the staff, maintain the filing systems, and handle every backup and repair yourself. Azure SQL Database is more like using a professionally staffed records office instead: the structure and rules for organizing records (a relational database) are still yours to define, but the day-to-day operation, maintenance, and backups are handled for you, so you can focus on using the records rather than running the office.
What Azure SQL Database is
Azure SQL Database is a fully managed relational database service, built on Microsoft SQL Server technology. As a PaaS offering, Azure handles infrastructure management, patching, and backups, letting the customer focus on their database design, queries, and data, rather than managing a database server themselves.
What "relational" means
A relational database organizes data into structured tables with defined relationships between them — for example, a "customers" table related to an "orders" table. This structure is well suited to data with clear, consistent relationships and where data integrity rules matter.
Key managed features
Automatic backups: Azure SQL Database automatically backs up data, supporting point-in-time restore.
Automatic patching: the underlying database engine is kept up to date without the customer needing to manage that process.
Built-in high availability: the service is designed with redundancy to help maintain availability, reducing the manual effort needed to achieve resilience.
Scalability: performance tiers can be adjusted based on the workload's needs.
How it compares to running SQL Server on a VM
An organization could instead install SQL Server on an Azure Virtual Machine (an IaaS approach) — giving more control over the database engine configuration, but requiring the customer to manage patching, backups, and high availability themselves. Azure SQL Database (PaaS) removes much of that management burden, at the cost of some lower-level control.
Design the relational schema
Tables, columns, and relationships are designed to structure the data appropriately for a relational database.
Create an Azure SQL Database
A database is created within Azure, choosing a performance tier appropriate for the workload's expected demand.
Let Azure handle maintenance
Azure automatically manages backups, patching, and infrastructure maintenance, reducing the customer's operational burden compared to a self-managed database.
Adjust performance tier as needed
As demand changes, the database's performance tier can be adjusted to provide more or less capacity, without the customer managing underlying hardware directly.
An e-commerce company stores its customer, order, and inventory data in Azure SQL Database, taking advantage of its structured, relational model to maintain consistent relationships between customers and their orders, while relying on Azure to handle backups and patching automatically.
A separate company that previously ran SQL Server on its own on-premises hardware migrates to Azure SQL Database to reduce the ongoing effort of managing database infrastructure themselves, while keeping the same familiar SQL Server-based querying and structure they were already using.
Objective 2.4 expects candidates to recognize Azure SQL Database as a managed, relational (structured) data service, and to understand what "managed" means in terms of reduced customer responsibility.
A common wrong answer is describing Azure SQL Database as suited for unstructured data — that's Blob Storage's role instead. Another common trap is assuming the customer still needs to manage patching and backups for Azure SQL Database — as a PaaS offering, Azure handles that.
Stable terms: Azure SQL Database, relational database, managed service. Recognizing SQL Database as the structured, relational counterpart to Blob Storage's unstructured focus is a frequently tested contrast.
Memory trick: Azure SQL Database = structured, relational data, with Azure handling the database management overhead (backups, patching) as a managed PaaS service.
Azure SQL Database is a fully managed, relational (structured) database service built on SQL Server technology.
As a PaaS offering, Azure handles infrastructure management, patching, and backups automatically.
Azure SQL Database suits structured data with defined relationships, unlike Blob Storage's focus on unstructured data.
Running SQL Server on a VM (IaaS) offers more control but requires the customer to manage more of the operational overhead themselves.
These come up on the exam all the time. Here's how to tell them apart.
Azure SQL Database (PaaS)
Azure manages patching and backups automatically
Less low-level control over the database engine
Faster to get started, less operational overhead
SQL Server on a VM (IaaS)
Customer manages patching and backups
More low-level control over the database engine configuration
More setup and ongoing operational responsibility
Mistake
Azure SQL Database is meant for unstructured data like images or videos.
Correct
Azure SQL Database is a relational database service for structured data with defined relationships — unstructured data like images and videos belongs in Blob Storage instead.
Mistake
The customer still needs to manage backups and patching for Azure SQL Database.
Correct
As a managed PaaS service, Azure handles backups and patching automatically — that's one of the key benefits over running a self-managed database on a VM.
Mistake
Azure SQL Database requires running it on a virtual machine you manage.
Correct
Azure SQL Database is a fully managed PaaS offering — it doesn't require the customer to provision or manage a virtual machine at all, unlike running SQL Server on an IaaS VM.
It's a fully managed, relational database service built on Microsoft SQL Server technology. Azure handles infrastructure management, patching, and backups, letting the customer focus on database design and data rather than server management.
No — as a managed PaaS service, Azure SQL Database automatically handles backups, including support for point-in-time restore, without the customer needing to configure or manage that process manually.
Azure SQL Database is a fully managed PaaS service — Azure handles patching, backups, and infrastructure. Running SQL Server on a VM is an IaaS approach, giving more low-level control over the database engine, but requiring the customer to manage patching, backups, and availability themselves.
You've just covered Azure SQL Database — now see how well it sticks with free AZ-900 practice questions. Full explanations included, no account needed.
Done with this chapter?