Your organization needs to migrate a critical, on-premises MySQL database to Cloud SQL for MySQL. The on-premises database is on a version of MySQL that is supported by Cloud SQL and uses the InnoDB s

Question

Options

• A
  1. Use Database Migration Service to connect to your on-premises database, and choose
• B
  1. Build a Cloud Data Fusion pipeline for each table to migrate data from the on-premises MySQL
• C
  1. Pause the on-premises applications.
• D1 Pause the on-premises applications.

• A
  73% (41)
• B
  18% (10)
• C
  4% (2)
• D
  5% (3)

Explanation

Options C and D both begin with 'Pause the on-premises applications,' which inherently causes downtime - eliminating them as candidates. Option B (Cloud Data Fusion pipelines per table) is a batch ETL approach that does not handle ongoing transactional changes or provide continuous replication, making it unsuitable for a live migration with minimal downtime. Option A (Database Migration Service, or DMS) is the correct answer and Google's recommended tool for this exact scenario. DMS uses MySQL binary log (binlog) replication to perform an initial full load of the database and then continuously replicate changes (CDC - change data capture) until a cutover is performed. This preserves transaction ordering and consistency, and the application downtime is reduced to only the final cutover window, typically seconds to minutes.

No community discussion yet for this question.