Instiq
Chapter 3 · Migrating data solutions·v1.0.0·Updated 6/15/2026·~13 min

What's changed: Created Professional Cloud Database Engineer Chapter 3 (Domain 3 "Migrate": strategy and planning = zero/near-zero downtime (continuous replication)/extended outage/fallback/DDL-DML conversion/reverse replication; tools and replication = Database Migration Service/Datastream (CDC)/Storage Transfer Service/Transfer Appliance/validation).

3.2Migration tools and replication

Key points

Understand choosing migration tools by scenario (Database Migration Service, Datastream, Storage Transfer Service, Transfer Appliance), migrating externally hosted databases, change data capture (CDC) replication, and validating migrations.

Once the strategy is set, choose the tool that fits the scenario—by DB type, acceptable downtime, data volume, and whether continuous changes occur.

3.2.1Choosing migration tools

ToolUse
Database Migration ServiceMinimal-downtime DB migration (homogeneous, some heterogeneous)
DatastreamCDC streaming of continuous changes
Storage Transfer ServiceTransfer large data over the network
Transfer AppliancePhysical shipping for huge data on thin networks

For minimal-downtime DB migration, Database Migration Service; to stream continuous changes via CDC, Datastream—externally hosted databases are also in scope. For bulk transfer, choose Storage Transfer Service (over network) or Transfer Appliance (physical) by requirements. After migration, confirm correctness with validation (row counts, consistency, sample comparison). Map "minimal-downtime DB migration = Database Migration Service" and "continuous change = Datastream (CDC)."

Exam point

Common: scenario → tool. E.g., "minimal-downtime DB migration" = Database Migration Service; "replicate continuous changes" = Datastream (CDC); "transfer bulk data online" = Storage Transfer Service; "huge data on a thin network" = Transfer Appliance; "confirm post-migration correctness" = validation (counts/consistency).

Warning

Watch the mix-ups: (1) Do not confuse Database Migration Service (DB migration), Datastream (CDC replication), and Storage Transfer/Transfer Appliance (file/object transfer). (2) Choose online (Storage Transfer) vs physical (Transfer Appliance) by bandwidth and deadline. (3) Close out migration with validation.

Diagram of Database Migration Service (min downtime)/Datastream (CDC)/Storage Transfer Service (online)/Transfer Appliance (physical), and post-migration validation.
Choose the right tool

3.2.2Section summary

  • DB migration = Database Migration Service; continuous-change replication = Datastream (CDC)
  • Bulk transfer = Storage Transfer Service (online)/Transfer Appliance (physical)
  • Confirm correctness with row-count/consistency validation after migration

Sign in to track progress — Log in.

Quick check

(just a quick review)

Q1. To migrate a database to Google Cloud with minimal downtime, which tool is best?

Q2. To stream-replicate continuous source-DB changes via CDC, which is best?

Q3. To migrate hundreds of TB with limited network bandwidth, which is best?

Q4. After migration completes, what should you first confirm?

Q5. To transfer large objects/files into Cloud Storage over the network, which is best?

Q6. Which correctly contrasts Database Migration Service and Datastream?

Check your understandingPractice questions for Chapter 3: Migrating data solutions