This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Choose the best response for each of the questions.
Approximately how long would the data transfer component of a fully optimized very large database (VLDB) migration to Azure take, if the database size is 30 TB?
3 hours.
15 hours.
30 hours.
In a very large database migration, commonly four export R3load servers are used. Typically, what is export server 1 dedicated to?
The largest 1-4 tables in the database
The largest 50-100 tables in the database
Any tables with table splits
When optimizing the source system for a very large database export, which solution should be used to run R3load processes?
UNIX server
Intel CPU
Either of the other choices, there's no significant difference in performance.
When migrating a very large database, what is the benefit of creating multiple clones of the source database and exporting in parallel?
Exporting is faster.
It reduces the chance of data loss or inconsistencies.
It allows larger databases to be migrated, which might otherwise exceed the migration size limit.
Given the following SQL statement for migrations: select session_id, request_id, start_time, status, command, wait_type, wait_resource, wait_time, last_wait_type, blocking_session_id from sys.dm_exec_requests where session_id >49 orderby wait_time desc; During the runtime of the database import, when and how often should the SQL statement be run?
Once, at the end of the import process.
Every few minutes throughout the import process.
Once at the start of the import process, and once at the end of the import process.
You must answer all questions before checking your work.
Was this page helpful?