Study guide

4.1 Evaluating Migration Requirements and Strategies

DP-300: Administering Microsoft Azure SQL Solutions Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current DP-300 Exam Facts 1.2 Skills Outline and Domain Weights 1.3 Study Strategy and Official Resources

2 Planning and Deploying Azure SQL Solutions

2.1 Choosing and Deploying Azure SQL Database Offerings 2.2 Automated Deployment, Azure Arc, and SQL Database in Microsoft Fabric 2.3 Table Partitioning and Sharding Strategy 2.4 Hybrid SQL Server and IaaS Patching

3 Configuring Resources for Scale and Performance

3.1 Configuring Azure SQL Database for Scale and Performance 3.2 Configuring Azure SQL Managed Instance for Scale and Performance 3.3 Configuring SQL Server on Azure VMs for Scale and Performance 3.4 Configuring Table Partitioning and Data Compression

4 Planning and Implementing a Migration Strategy

4.1 Evaluating Migration Requirements and Strategies 4.2 Implementing Online, Offline, and Azure Migrations 4.3 Migrating Between Azure SQL Services and Troubleshooting

5 Configuring Database Authentication and Authorization

5.1 Microsoft Entra ID Authentication for Azure SQL 5.2 Authentication for SQL on Azure VMs and Managed Instance; Troubleshooting 5.3 Security Principals and Entra-Backed Users 5.4 Permissions, Least Privilege, and T-SQL Management

6 Implementing Security for Data at Rest and in Transit

6.1 Transparent Data Encryption and Object-Level Encryption 6.2 Always Encrypted and VBS Enclaves 6.3 Firewall Rules, Private Links, and Service Endpoints

7 Implementing Compliance Controls for Sensitive Data

7.1 Data Classification and Server/Database Auditing 7.2 Change Data Tracking and Dynamic Data Masking 7.3 Row-Level Security and Ledger in Azure SQL

8 Monitoring Resource Activity and Performance

8.1 Operational Baselines and Performance Metric Sources 8.2 Interpreting Metrics and Configuring Activity Monitoring 8.3 Monitoring with Database Watcher (Preview) 8.4 Monitoring with Extended Events

9 Monitoring and Optimizing Query Performance

9.1 Configuring and Monitoring with Query Store 9.2 Session Blocking and Dynamic Management Views 9.3 Index Changes and Execution Plan Review 9.4 Query Construct Modifications and Intelligent Insights

10 Configuring Database Solutions for Optimal Performance

10.1 Index, Statistics, and Integrity Maintenance 10.2 Automatic Tuning and Database-Scoped Configuration 10.3 Server Settings and Resource Governor 10.4 Compute/Storage Scaling and Intelligent Query Processing

11 Creating and Managing SQL Server Agent Jobs

11.1 Schedules for Regular Maintenance Jobs 11.2 Job Alerts, Notifications, and Agent Troubleshooting 11.3 Automating Deployment with ARM and Bicep Templates

12 Automating Deployments and Database Tasks in Azure

12.1 Azure PowerShell, Azure CLI, and Deployment Monitoring 12.2 Elastic Jobs for Cross-Database Automation 12.3 Azure Automation Runbooks, Alerts, and Troubleshooting Automated Tasks

13 Planning an HA/DR Strategy and Backup and Restore

13.1 Recommending HA/DR Strategy from RPO and RTO 13.2 Hybrid and Azure-Specific HA/DR Solutions and Testing 13.3 Backup and Restore Strategy with Native Tools 13.4 Point-in-Time Restore and Recovery Operations

14 Configuring HA/DR: Long-Term Retention, Geo-Replication, and Failover Groups

14.1 Long-Term Retention, T-SQL Backup/Restore, and Cloud Storage 14.2 Active Geo-Replication 14.3 Failover Groups

15 Advanced HA/DR: Availability Groups, FCIs, Log Shipping, and Troubleshooting

15.1 Always On Availability Groups on SQL Managed Instance and Azure VMs 15.2 Always On Failover Cluster Instances and Log Shipping 15.3 Monitoring and Troubleshooting HA/DR Solutions

4.1 Evaluating Migration Requirements and Strategies

Key Takeaways Explain This Topic AI

A migration assessment starts with Data Migration Assistant (DMA) for compatibility and feature parity, then Database Experimentation Assistant (DEA) to capture and replay the production workload against the target

Offline migrations incur full downtime during the copy window; online migrations use change data capture or replication to keep the target synchronized and limit downtime to the final cutover

RPO defines the maximum acceptable data loss measured in time; RTO defines the maximum acceptable downtime, and both must be specified for the migration itself, not just for normal operations

Target selection (Azure SQL Database, SQL Managed Instance, or SQL Server on VM) is driven by instance-level feature parity: cross-database queries, SQL Agent, linked servers, and CLR push toward Managed Instance or VM

Sizing the target uses DMA performance baselines plus a 20-30% headroom buffer; network prerequisites include ExpressRoute or VPN bandwidth sized to the initial snapshot plus ongoing delta throughput

Last updated: August 2026

Why Migration Planning Is a DP-300 Exam Pillar

The DP-300 exam weights Plan and implement data platform resources at 15-20%, and a large slice of that domain is migration strategy. Azure offers three broadly compatible SQL Server targets - Azure SQL Database (single database), Azure SQL Managed Instance (instance-scoped PaaS), and SQL Server on Azure VMs (IaaS lift-and-shift) - and a frequent exam pattern is matching a workload's feature surface to the right target. The planning phase is where that decision is made, and it rests on three activities: assess the source, choose the target by feature parity, and pick an offline or online path that respects the business's downtime tolerance.

Source and Target Assessment

Assessment begins with the Data Migration Assistant (DMA) , a free Microsoft tool that scans a SQL Server source and produces a compatibility report. DMA answers two questions in one pass:

Compatibility issues : features or behaviors that will break on the chosen target - for example, cross-database queries on Azure SQL Database, SQL Server Agent jobs on Azure SQL Database, or specific deprecated syntax.

Feature parity / recommendations : which target SKU and tier the workload fits, plus partial or unsupported features that need a redesign (such as OPENROWSET with provider names, filestream, or T-SQL endpoints).

DMA classifies each finding by impact (Error, Warning, Information) and by migration blocker versus post-migration optimization. A migration blocker must be fixed before cutover; a warning can be remediated after. The exam often contrasts DMA with the Database Experimentation Assistant (DEA) , which is workload-based, not static: DEA captures a trace of the production workload, replays it against the source and the target, and produces an A/B comparison report showing query-level performance regressions. The canonical two-tool pattern is DMA for static schema/config assessment, then DEA for behavioral validation under the real workload.

Target Selection by Feature Parity

The target choice is driven by which instance-level features the workload depends on. The exam's decision matrix looks like this:

  • Workload need Azure SQL Database SQL Managed Instance SQL Server on VM
  • Cross-database queries / USE statements Not supported Supported Supported
  • SQL Server Agent jobs Not supported Supported (native) Supported (native)
  • Linked servers Limited Supported Supported
  • CLR / external assemblies Limited Supported Supported
  • Filestream / FileTable Not supported Not supported Supported
  • Windows authentication (on-prem AD) Not directly; Entra ID mapping Entra ID + Windows auth passthrough Full
  • Engine patching / OS patching Fully managed Fully managed You own it

The rule of thumb the exam tests: Azure SQL Database is the default when the workload is a self-contained application database with no instance-level dependencies. SQL Managed Instance is the answer when the workload needs instance scope (Agent, linked servers, cross-database queries, native Service Broker) but the team wants to retire OS and engine patching. SQL Server on Azure VM is the escape hatch when the workload depends on features that PaaS cannot provide - Windows authentication against a legacy domain, filestream, third-party services on the same box, or full control of tempdb placement and trace flags.

Compatibility Level and Version Targeting

Each database carries a compatibility level (for example, 130 for SQL Server 2016, 150 for SQL Server 2019, 160 for SQL Server 2022). Lowering the compatibility level preserves some legacy optimizer behaviors and can be a temporary migration aid, but it does not make an unsupported feature suddenly work. The exam trap is conflating compatibility level with feature parity: a database at compat level 130 still cannot use cross-database queries on Azure SQL Database. Keep the compatibility level at the source value at cutover to preserve behavior, raise it later in a controlled change after validating performance with Query Store.