You have an on-premises SAP NetWeaver deployment that uses Windows Server 2016 and Microsoft SQL Server 2016. You need to migrate the deployment to an Azure virtual machine that runs Windows Server…

Question

Options

• Aheterogeneous SAP classical migration
• Bclassical SAP Database Migration Option (DMO)
• Clift-and-shift
• DAzure Migrate

• A
  4% (1)
• B
  9% (2)
• C
  83% (19)
• D
  4% (1)

Explanation

Lift-and-shift is correct because the OS platform (Windows Server 2016) remains unchanged and the database stays within the same vendor family - SQL Server 2016 to SQL Server 2019 is a version upgrade, not a platform change. This makes it a homogeneous migration: you back up the SAP system and SQL Server databases on-premises and restore them onto the Azure VM, then upgrade SQL Server in place.

Option A (Heterogeneous classical migration) is wrong because that method is reserved for cross-platform scenarios - such as moving from Windows to Linux or from one database vendor to another (e.g., Oracle → SAP HANA). Option B (Classical DMO) is wrong because DMO is specifically designed for simultaneously migrating the database to SAP HANA and upgrading the SAP application in one step - it doesn't apply when staying on SQL Server. Option D (Azure Migrate) is a general-purpose VM discovery and migration service; while useful for bulk workload assessments, SAP migrations require SAP-specific methods to preserve application integrity.

Memory tip: Think of it as a two-question filter - Did the OS family change? Did the database vendor change? If both answers are "no," it's lift-and-shift. Only flip to "heterogeneous" or "DMO" when you're crossing platform or vendor boundaries.

No community discussion yet for this question.