68
Design a Data Storage Solution for Relational Data
●● Recommend database service tier sizing
●● Recommend a solution for database scalability
●● Recommend a solution for encrypting data at rest, data in transmission, and data in use
Recommend a Data Storage Solution
●● Recommend a solution for storing relational data
Prerequisites
●● Working experience with database solutions
●● Conceptual knowledge of SQL Server
Design for Azure SQL databases
The CTO has asked you to design databases for Azure to meet all of the needs of existing structured data
on premises and suggestion solutions for any new relational data workloads that Tailwinds might need.
Structured data includes relational data and has a shared schema. Structured data is often stored in
database tables with rows, columns, and keys. Structured data is often used for application storage like an
ecommerce website.
Within the umbrella of the Azure SQL platform, there are many deployment options and choices that you
need to make to meet your needs. These options give you the flexibility to get and pay for exactly what
you need. Here, we'll cover some of the considerations you need to make when you choose various Azure
SQL deployment options. We'll also cover some of the technical specifications for each of these options.
The deployment options discussed here include SQL Server on virtual machines, Azure SQL Managed
Instance, Azure SQL Database, Azure SQL Managed Instance pools, and Azure SQL Database elastic
database pools.
Analyze Azure SQL deployment options
As displayed in the following graphic, Azure offers SQL Server in the following ways:
●● SQL Server on Azure VMs
●● Managed instances:
●● Single instances
●● Instance pool
●● Databases:
●● Single database
●● Elastic pool
