0
0
Azurecloud~30 mins

Azure SQL Database vs SQL Managed Instance - Hands-On Comparison

Choose your learning style9 modes available
Azure SQL Database vs SQL Managed Instance
📖 Scenario: You are working as a cloud engineer for a company that wants to move its database workloads to Azure. The company needs to understand the differences between Azure SQL Database and SQL Managed Instance to choose the right service for their needs.
🎯 Goal: Build a simple comparison setup in Azure that shows the basic configuration of an Azure SQL Database and a SQL Managed Instance. This will help the company see how each service is created and configured.
📋 What You'll Learn
Create an Azure SQL Database resource with a specific name and configuration
Create an Azure SQL Managed Instance resource with a specific name and configuration
Add configuration variables for performance tier and storage size
Apply tags to both resources for environment and project identification
💡 Why This Matters
🌍 Real World
Companies moving databases to Azure need to choose between Azure SQL Database and SQL Managed Instance based on their workload requirements. This project shows how to set up both services.
💼 Career
Cloud engineers and database administrators use these skills to deploy and manage Azure database services securely and efficiently.
Progress0 / 4 steps
1
Create Azure SQL Database resource
Create an Azure SQL Database resource named mySqlDatabase with the server name mySqlServer and the edition set to Basic.
Azure
Need a hint?

Start by defining an azurerm_sql_server resource with the name mySqlServer. Then create an azurerm_sql_database resource named mySqlDatabase that uses this server and sets the edition to Basic.

2
Add configuration variables for performance and storage
Add two variables: performance_tier set to GeneralPurpose and storage_size_gb set to 32. These will be used to configure the SQL Managed Instance.
Azure
Need a hint?

Use variable blocks to define performance_tier and storage_size_gb with the specified default values.

3
Create Azure SQL Managed Instance resource
Create an Azure SQL Managed Instance resource named mySqlManagedInstance using the variables performance_tier and storage_size_gb for its configuration. Set the resource group to myResourceGroup and location to eastus.
Azure
Need a hint?

Create an azurerm_sql_managed_instance resource named mySqlManagedInstance. Use the variables performance_tier and storage_size_gb for the SKU and storage size. Use a placeholder subnet ID for now.

4
Add tags to both resources
Add tags to both mySqlDatabase and mySqlManagedInstance resources. Use the tags environment = "dev" and project = "database-migration".
Azure
Need a hint?

Add a tags block inside both resource definitions with the keys environment and project set to the specified values.