AZ-120 · Question #128
You have an on-premises SAP landscape that contains a 20-TB IBM DB2 database. The database contains large tables that are optimized for read operations via secondary indexes. You plan to migrate the…
The correct answer is D. deleting secondary indexes. Secondary indexes for very large tables can be removed from the STR file and built ONLINE with scripts after the main portion of the import has finished and post processing tasks such as configuring STMS are occurring…
Question
You have an on-premises SAP landscape that contains a 20-TB IBM DB2 database. The database contains large tables that are optimized for read operations via secondary indexes. You plan to migrate the database platform to SQL Server on Azure virtual machines. You need to recommend a database migration approach that minimizes the time of the export stage. What should you recommend?
Options
- ASAP Database Migration Option (DMO) in parallel transfer mode
- Btable splitting
- Clog shipping
- Ddeleting secondary indexes
How the community answered
(36 responses)- A17% (6)
- B3% (1)
- C8% (3)
- D72% (26)
Explanation
Secondary indexes for very large tables can be removed from the STR file and built ONLINE with scripts after the main portion of the import has finished and post processing tasks such as configuring STMS are occurring. https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/very-large-database- migration-to-azure-8211-recommendations/ba-p/368146
Topics
Community Discussion
No community discussion yet for this question.