Azure SQL Database vs SQL Managed Instance - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create an Azure SQL Database using the Azure CLI.

Azure

az sql db create --resource-group myResourceGroup --server myServer --name [1] --service-objective S0

Drag options to blanks, or click blank then click option'

AmyDatabase

BmyResourceGroup

CmyServer

DS0

Attempts:

3 left

💡 Hint

Common Mistakes

Using the server name instead of the database name.

Confusing resource group with database name.

The --name parameter specifies the name of the Azure SQL Database to create.

2fill in blank

medium

Complete the code to create an Azure SQL Managed Instance using the Azure CLI.

Azure

az sql mi create --name [1] --resource-group myResourceGroup --vnet-name myVnet --subnet mySubnet --admin-user adminUser --admin-password myPassword

Drag options to blanks, or click blank then click option'

AmyDatabase

BmyManagedInstance

CmyServer

DmyResourceGroup

Attempts:

3 left

💡 Hint

Common Mistakes

Using database name instead of Managed Instance name.

Confusing resource group with Managed Instance name.

The --name parameter specifies the name of the Managed Instance to create.

3fill in blank

hard

Fix the error in the command to create an Azure SQL Database with a performance tier.

Azure

az sql db create --resource-group myResourceGroup --server myServer --name myDatabase --[1] S3

Drag options to blanks, or click blank then click option'

Atier

Bperformance-tier

Cservice-objective

Dperformance-level

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect parameter names like 'performance-tier' or 'tier'.

Misspelling the parameter name.

The correct parameter to specify the performance tier is --service-objective.

4fill in blank

hard

Fill both blanks to configure a subnet for Azure SQL Managed Instance with the required delegation and service endpoints.

Azure

az network vnet subnet update --name [1] --vnet-name myVnet --resource-group myResourceGroup --delegations [2]

Drag options to blanks, or click blank then click option'

AmySubnet

BMicrosoft.Sql/managedInstances

CMicrosoft.Sql/servers

DMicrosoft.Network/virtualNetworks

Attempts:

3 left

💡 Hint

Common Mistakes

Using server delegation instead of managed instance delegation.

Using wrong subnet name.

The subnet name is mySubnet and the delegation for Managed Instance is Microsoft.Sql/managedInstances.

5fill in blank

hard

Fill all three blanks to write a PowerShell command that creates an Azure SQL Database with a specified edition and max size.

Azure

New-AzSqlDatabase -ResourceGroupName myResourceGroup -ServerName myServer -DatabaseName [1] -Edition [2] -MaxSizeBytes [3]

Drag options to blanks, or click blank then click option'

ATestDB

BStandard

C2147483648

DBasic

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect edition names.

Setting max size in wrong units.

The database name is TestDB, edition is Standard, and max size is 2147483648 bytes (2 GB).

Practice

1. Which Azure service provides a fully managed single database with simple setup and maintenance?

easy

A. Azure Cosmos DB

B. SQL Managed Instance

C. Azure Blob Storage

D. Azure SQL Database

Solution

1. Step 1: Understand service purpose

   Azure SQL Database is designed as a simple, fully managed single database service in the cloud.

2. Step 2: Compare with other options

   SQL Managed Instance offers more features and compatibility but is not as simple as Azure SQL Database. Blob Storage and Cosmos DB serve different purposes.

3. Final Answer:

   Azure SQL Database -> Option D

4. Quick Check:

   Simple managed single database = Azure SQL Database [OK]

Hint: Simple managed single DB? Think Azure SQL Database [OK]

Common Mistakes:

• Confusing SQL Managed Instance with Azure SQL Database
• Choosing storage services like Blob Storage
• Selecting Cosmos DB which is NoSQL

2. Which option correctly describes a key feature of SQL Managed Instance in Azure?

easy

A. Limited SQL Server compatibility

B. Only supports single databases

C. Full SQL Server compatibility with network control

D. No support for SQL Server Agent

Solution

1. Step 1: Identify SQL Managed Instance features

   SQL Managed Instance offers full SQL Server compatibility and allows more control over network settings.

2. Step 2: Eliminate incorrect options

   It supports SQL Server Agent and multiple databases, so options A, B, and C are incorrect.

3. Final Answer:

   Full SQL Server compatibility with network control -> Option C

4. Quick Check:

   Full compatibility + network control = SQL Managed Instance [OK]

Hint: Full SQL Server features? Choose SQL Managed Instance [OK]

Common Mistakes:

• Thinking SQL Managed Instance has limited compatibility
• Believing it does not support SQL Server Agent
• Confusing single database support with Azure SQL Database

3. Given an application requiring SQL Server Agent jobs and linked server support, which Azure service will work without modification?

medium

A. Azure SQL Database

B. SQL Managed Instance

C. Azure Table Storage

D. Azure Data Lake

Solution

1. Step 1: Check feature support

   SQL Managed Instance supports SQL Server Agent jobs and linked servers, unlike Azure SQL Database.

2. Step 2: Match application needs

   The app needs these features without changes, so SQL Managed Instance fits best.

3. Final Answer:

   SQL Managed Instance -> Option B

4. Quick Check:

   SQL Server Agent + linked servers = SQL Managed Instance [OK]

Hint: Needs SQL Server Agent? Pick SQL Managed Instance [OK]

Common Mistakes:

• Assuming Azure SQL Database supports SQL Server Agent
• Confusing storage services with database services
• Ignoring linked server requirements

4. A developer tries to migrate an on-premises SQL Server database with cross-database queries to Azure SQL Database but faces errors. What is the likely cause?

medium

A. Azure SQL Database does not support cross-database queries

B. SQL Managed Instance does not support cross-database queries

C. On-premises SQL Server uses unsupported data types

D. Azure SQL Database requires manual schema conversion

Solution

1. Step 1: Understand cross-database query support

   Azure SQL Database does not support cross-database queries natively, causing errors.

2. Step 2: Compare with SQL Managed Instance

   SQL Managed Instance supports cross-database queries, so it's not the cause.

3. Final Answer:

   Azure SQL Database does not support cross-database queries -> Option A

4. Quick Check:

   Cross-database queries missing in Azure SQL Database [OK]

Hint: Cross-database queries fail? Check Azure SQL Database limits [OK]

Common Mistakes:

• Blaming SQL Managed Instance for cross-database query issues
• Assuming all data types are supported without checking
• Ignoring Azure SQL Database feature limits

5. You need to move a legacy app using SQL Server features like linked servers, SQL Server Agent jobs, and cross-database queries to Azure with minimal changes. Which service should you choose and why?

hard

A. SQL Managed Instance, because it supports full SQL Server features and network control

B. Azure SQL Database, because it is simpler and fully managed

C. Azure Cosmos DB, because it supports multiple data models

D. Azure Blob Storage, because it stores large amounts of data

Solution

1. Step 1: Identify required SQL Server features

   The app uses linked servers, SQL Server Agent jobs, and cross-database queries which require full SQL Server compatibility.

2. Step 2: Match features to Azure services

   SQL Managed Instance supports these features and network control, enabling minimal changes during migration.

3. Final Answer:

   SQL Managed Instance, because it supports full SQL Server features and network control -> Option A

4. Quick Check:

   Legacy SQL Server features need SQL Managed Instance [OK]

Hint: Legacy SQL Server features? Use SQL Managed Instance [OK]

Common Mistakes:

• Choosing Azure SQL Database despite missing features
• Confusing Cosmos DB or Blob Storage as SQL replacements
• Ignoring network control needs