Database Reference
In-Depth Information
using added hardware (in addition to any interim hardware for the database copy) for ex-
treme downtime reduction.
This tactic is the most expensive option, but should be considered if the size of the system
and the duration of the migration constitute an unmitigated risk. However, upgrades and
Unicode conversions must be executed separately.
Classic OS/DB migration using SWPM
Using the Software Provisioning Manager (SWPM) is the right tactic if no upgrade or
Unicode conversion is required. This option allows for the traditional export and import
of a database for a heterogeneous migration from any database to any database, including
HANA. The export and import can be performed sequentially or in parallel depending on
the hardware available.
This tactic is not suitable for upgrades or Unicode conversions, because each of these ad-
ditional tasks would have to be executed separately.
Upgrade and migration using DMO for SUM
If an upgrade or Unicode conversion is required, and an XXL migration is too costly, then
using the Database Migration Option (DMO) is the best choice. DMO works with the SAP
Upgrade Manager (SUM) to deliver a system upgrade, Unicode conversion, and HANA
migration in one step.
In order to understand the benefits of DMO, you first need to understand the other migra-
tion options above, which require separate activities to perform upgrades, Unicode conver-
sion, and database migrations.
For example, in a downtime-minimized approach, the delta queues are cloned, then the leg-
acy database is copied and restored, then the Unicode conversion would require an export/
import of the database, then the upgrade, and then the HANA migration. The result is too
many steps and the process lacks efficiency.
Therefore, the benefit of using DMO for SUM is clear: a more efficient way to migrate to
SAP HANA while also executing an SAP BW 7.40 upgrade and a Unicode conversion (if
required). This simplification reduces the overall migration duration, even for extra-large
