Database Reference
In-Depth Information
large database such as one greater than 40 TB. The next section takes a closer look at the
different tactics for migrating to SAP HANA.
1.1.3
Database migration tactics
With a migration approach selected, it is time to dive into the detailed migration procedures
available. The specific tactics employed to migrate an existing database to SAP HANA will
depend on the other activities which are part of the objective.
Extra-large migration (legacy database > 50 TB)
Upgrade to SAP BW 7.40
Unicode conversion
If the legacy database is larger than 50 TB, then an XXL migration service from SAP may
be worth consideration. The XXL migration service is a customer-specific process tailored
by SAP professionals for each customer's needs.
To operate SAP BW on HANA, the minimum version required is version 7.30 SP05. The
latest version of SAP BW is 7.40 SP10. If there is no need to perform an upgrade as part of
the migration, then a classic OS/DB migration is the appropriate tactic.
However, if an upgrade to SAP BW 7.40 is also required or desired and/or a Unicode con-
version is required, then a migration using DMO for SUM is the best tactic.
In the next three sections, we cover each of these tactics in more detail.
Extra-large migration using XXL service
If the legacy database is larger than 50 TB uncompressed, then the migration phase alone
could exceed four days at an average throughput of 0.5 TB per hour—please note this does
not take into account all the pre-migration and post-migration tasks, which could add a
week or more to the total duration. A duration of this magnitude could pose a risk when
catching up data loads from the cloned delta queues.
The XXL migration process is a HANA-specific binary export/import which is tailored for
your system and is delivered and executed by SAP professionals. It is a scalable approach
