Migrating data from Yandex Managed Service for MySQL® to Yandex Managed Service for Greenplum®

You can set up data transfer from Managed Service for MySQL® to Managed Service for Greenplum® databases using Data Transfer. To do this:

1. Prepare the test data.
2. Create a database in the target cluster.
3. Prepare and activate the transfer.
4. Test the transfer.

If you no longer need the resources you created, delete them.

Getting startedGetting started

Prepare the infrastructure:

Prepare the test dataPrepare the test data

1. Connect to the mmy_db database in the Managed Service for MySQL® source cluster.

2. Create a simple table named table1:

   CREATE TABLE table1 (
   id int NOT NULL,
   name varchar (10),
   PRIMARY KEY (id)
   );
   

3. Populate the table with data:

   INSERT INTO table1 VALUES
   (1, 'Name1'),
   (2, 'Name2'),
   (3, 'Name3');
   

Create a database in the target clusterCreate a database in the target cluster

1. Connect to the auxiliary postgres database in the Managed Service for Greenplum® target cluster as mgp_user.

2. Create a database named mgp_db:

   CREATE DATABASE mgp_db;
   

Prepare and activate the transferPrepare and activate the transfer

1. Create a target endpoint of the Greenplum® type and specify the cluster connection parameters in it:

   • Connection type: Managed Service for Greenplum cluster.
   • Managed Service for Greenplum cluster: <name_of_Greenplum®_target_cluster> from the drop-down list.
   • Database: mgp_db.
   • User: mgp_user.
   • Password: <user_password>.

2. Create a source endpoint and a transfer.

   Manually

   Using Terraform

   1. Create a source endpoint of the MySQL® type and specify the cluster connection parameters in it:

      • Connection type: Managed Service for MySQL cluster.
      • Managed Service for MySQL cluster: <name_of_MySQL®_source_cluster> from the drop-down list.
      • Database: mmy_db.
      • User: mmy_user.
      • Password: <user_password>.

   2. Create a transfer of the Snapshot and replication type that will use the created endpoints.

   3. Activate the transfer and wait for its status to change to Replicating.

   1. In the mmy-to-mgp.tf file, specify the following parameters:

      • target_endpoint_id: Target endpoint ID.
      • transfer_enabled: 1 to create a transfer.

   2. Check that the Terraform configuration files are correct using this command:

      terraform validate
      

      If there are any errors in the configuration files, Terraform will point them out.

   3. Create the required infrastructure:

      1. Run the command to view planned changes:

         terraform plan
         

         If the resource configuration descriptions are correct, the terminal will display a list of the resources to modify and their parameters. This is a test step. No resources are updated.

      2. If you are happy with the planned changes, apply them:

         1. Run the command:

            terraform apply
            

         2. Confirm the update of resources.

         3. Wait for the operation to complete.

   4. The transfer will be activated automatically. Wait for its status to change to Replicating.

Test the transferTest the transfer

Check the transfer performance by testing the copy and replication processes.

Test the copy processTest the copy process

1. Connect to mgp_db in the Managed Service for Greenplum® target cluster.

2. Run the following query:

   SELECT * FROM mmy_db.table1;
   

Test the replication processTest the replication process

1. Connect to the mmy_db database in the Managed Service for MySQL® source cluster.

2. Populate the table1 table with data:

   INSERT INTO table1 VALUES
   (4, 'Name4');
   

3. Make sure the new row has been added to the target database:

   1. Connect to mgp_db in the Managed Service for Greenplum® target cluster.

   2. Run the following query:

      SELECT * FROM mmy_db.table1;
      

Delete the resources you createdDelete the resources you created

Some resources are not free of charge. To avoid paying for them, delete the resources you no longer need: