Change Data Capture

Related topics

• Change Data Capture is part of continuous migration From the official documentation: “With **continuous** migrations, your data is migrated in two phases: full dump, and Change Data Capture (CDC).”
• Change Data Capture is part of migration job From the official documentation: “If the migration job is stopped during the change data capture (CDC) phase, then you can promote or delete the job.”
• Database Migration Service depends on Change Data Capture From the official documentation: “Database Migration Service requires that you enable the change data capture mechanism on your source database for the migration.”
• Cloud SQL works with Database Migration Service From the official documentation: “Gives Cloud Database Migration service account access to Cloud SQL resources.”
• migration job is part of Database Migration Service From the official documentation: “Creating and running the migration job in Database Migration Service.”
• Cloud SQL works with Cloud Storage From the official documentation: “Exports data from a Cloud SQL instance to a Cloud Storage bucket as a SQL dump or CSV file.”
• Cloud Storage works with Database Migration Service From the official documentation: “Database Migration Service replicates data from SQL Server backup and transaction log files that you upload to a Cloud Storage bucket.”
• Cloud Monitoring works with Cloud SQL From the official documentation: “You can also get more details by viewing the Cloud Monitoring logs for your Cloud SQL destination instance.”
• Cloud Monitoring works with Database Migration Service From the official documentation: “To view more details about the error, navigate to Cloud Monitoring using the link on the migration job. The logs are filtered to the specific migration job.”
• Cloud Monitoring works with migration job From the official documentation: “To view more details about the error, navigate to Cloud Monitoring using the link on the migration job.”
• Cloud SQL works with migration job From the official documentation: “To run a migration job from a source which includes such metadata, create the users on your destination Cloud SQL instance before starting your migration job.”
• continuous migration is part of Database Migration Service From the official documentation: “For homogeneous MySQL migrations to Cloud SQL, Database Migration Service supports *continuous* and *one-time* migration flows.”
• Database Migration Service depends on Cloud SQL From the official documentation: “For heterogeneous Oracle migrations to Cloud SQL, Database Migration Service requires that you first create and configure your Cloud SQL destination instance.”
• Cloud SQL depends on Cloud Storage From the official documentation: “When ingesting data from Cloud SQL, data is first staged to a Cloud Storage bucket.”
• Cloud Storage works with migration job From the official documentation: “You can configure whether the migration job can use differential backup files from the Cloud Storage bucket.”
• Database Migration Service depends on Cloud Storage From the official documentation: “If you use file export and import to migrate, or use the Database Migration Service migration tool, you need to create a Cloud Storage bucket.”