By: Edward Bell, Solutions Architect,
[Striim, Inc](https://www.striim.com/).
This tutorial demonstrates how to migrate a MySQL database to
[Spanner](https://docs.cloud.google.com/spanner/docs)
using Striim. Striim is a comprehensive streaming
[extract, transform, and load (ETL)](https://wikipedia.org/wiki/Extract,_transform,_load)
platform that enables online database migrations and continuous streaming
replication from on-premises and cloud data sources to Google Cloud data
services.
This tutorial focuses on the implementation of a continuous migration from
[Cloud SQL for MySQL](https://docs.cloud.google.com/sql/docs/mysql)
to Spanner, and is not an explanation of migrations or replications, or
why you might want to migrate your underlying database.
This tutorial is intended for database administrators, IT professionals, and
cloud architects interested in using Spanner---a scalable,
enterprise-grade, globally distributed, and strongly consistent database service
built for the cloud.
## Objectives
- Use Google Cloud Marketplace to deploy Striim.
- Use Striim to read from a source Cloud SQL for MySQL database.
- Use Striim to continuously replicate from Cloud SQL for MySQL to Spanner.
## Costs
In this document, you use the following billable components of Google Cloud:
- [Compute Engine](https://cloud.google.com/compute/vm-instance-pricing)
- [Cloud SQL for MySQL](https://docs.cloud.google.com/sql/pricing)
- [Spanner](https://docs.cloud.google.com/spanner/pricing)
To generate a cost estimate based on your projected usage,
use the [pricing calculator](https://docs.cloud.google.com/products/calculator).
New Google Cloud users might be eligible for a [free trial](https://docs.cloud.google.com/free).
This tutorial also uses Striim, which includes a trial period through the
[Cloud Marketplace](https://console.cloud.google.com/marketplace/details/striim/striim).
When you finish the tasks that are described in this document, you can avoid
continued billing by deleting the resources that you created. For more information, see
[Clean up](https://docs.cloud.google.com/architecture/partners/continuous-data-replication-cloud-spanner-striim#clean-up).
## Before you begin
1. In the Google Cloud console, on the project selector page,
select or create a Google Cloud project.
**Roles required to select or create a project**
- **Select a project**: Selecting a project doesn't require a specific IAM role---you can select any project that you've been granted a role on.
- **Create a project** : To create a project, you need the Project Creator role (`roles/resourcemanager.projectCreator`), which contains the `resourcemanager.projects.create` permission. [Learn how to grant
roles](https://docs.cloud.google.com/iam/docs/granting-changing-revoking-access).
> [!NOTE]
> **Note**: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.
[Go to project selector](https://console.cloud.google.com/projectselector2/home/dashboard)
2.
[Verify that billing is enabled for your Google Cloud project](https://docs.cloud.google.com/billing/docs/how-to/verify-billing-enabled#confirm_billing_is_enabled_on_a_project).
3.
Enable the Compute Engine and Spanner APIs, if any are not already enabled.
**Roles required to enable APIs**
To enable APIs, you need the `serviceusage.services.enable` permission. If you
created the project, then you likely already have this permission through the
Owner role (`roles/owner`). Otherwise, you can get this permission through the
Service Usage Admin role (`roles/serviceusage.serviceUsageAdmin`).
[Learn how to grant roles](https://docs.cloud.google.com/iam/docs/granting-changing-revoking-access).
[Enable the APIs](https://console.cloud.google.com/apis/enableflow?apiid=compute.googleapis.com,spanner.googleapis.com)
4. In the Google Cloud console, activate Cloud Shell.
[Activate Cloud Shell](https://console.cloud.google.com/?cloudshell=true)
5. Set the default compute zone to `us-central1-a`:
gcloud config set compute/zone us-central1-a
export COMPUTE_ZONE=us-central1-a
This zone is where you deploy your database and compute resources to. For
more information about zones, see
[Geography and regions](https://docs.cloud.google.com/docs/geography-and-regions).
## Create a Cloud SQL for MySQL instance
You create a Cloud SQL for MySQL virtual machine (VM) instance that you
later connect to Striim. In this case, the instance acts as the source
transactional system that you later replicate. In a real-world scenario, the
source database can be one of many transactional database systems either
on-premises or in other clouds.
1. In Cloud Shell, create the environment variables to create the
instance:
CSQL_NAME=striim-sql-src
CSQL_USERNAME=striim-user
CSQL_USER_PWD=$(openssl rand -base64 18)
CSQL_ROOT_PWD=$(openssl rand -base64 18)
If you close the Cloud Shell session, you lose the variables.
2. Make a note of the `CSQL_USER_PWD` and `CSQL_ROOT_PWD` passwords
generated by the following commands:
echo $CSQL_USER_PWD
echo $CSQL_ROOT_PWD
3. Create the Cloud SQL for MySQL instance:
gcloud sql instances create $CSQL_NAME \
--root-password=$CSQL_ROOT_PWD --zone=$COMPUTE_ZONE \
--tier=db-n1-standard-2 --enable-bin-log
4. Create a Cloud SQL for MySQL user that Striim can connect to:
gcloud sql users create $CSQL_USERNAME --instance $CSQL_NAME \
--password $CSQL_USER_PWD --host=%
The Cloud SQL for MySQL database is set up for Striim to read.
5. Find the IP address of the Cloud SQL for MySQL instance:
gcloud sql instances list
Write down the IP address listed in the `PRIMARY_ADDRESS` column.
## Set up Striim
To set up an instance of the Striim server software, you use the
Cloud Marketplace.
1. In the Google Cloud console, go to the **Striim** page in the
Cloud Marketplace.
[Go to Striim in the Cloud Marketplace](https://console.cloud.google.com/marketplace/details/striim/striim)
2. Click **Launch**.
3. In the **New Striim Deployment** window, complete the following fields:
- Select the project that you created or selected to use for this tutorial.
- In the **Zone** drop-down menu, select **`us-central1-a`**.
- If you accept the terms of service, select the **I accept the
Google Cloud Marketplace Terms of Service** checkbox.
Cloud Marketplace solutions typically come with various
resources that launch to support the software. Review the monthly
billing estimate before launching the solution.
- Leave all other settings at their default values.
4. Click **Deploy**.
5. In the Google Cloud console, go to the **Deployments** page.
[Go to Deployments](https://console.cloud.google.com/dm/deployments)
6. To review the deployment details of the Striim instance, click the name
of the Striim instance. Write down the name of the deployment, as well
as the name of the VM that has deployed.
7. To allow Striim to communicate with Cloud SQL for MySQL,
[add the Striim server's IP address](https://docs.cloud.google.com/sql/docs/mysql/connect-external-app)
to the Cloud SQL for MySQL instance's authorized networks:
```
STRIIMVM_NAME=STRIIM_VM_NAME
STRIIMVM_ZONE=us-central1-a
gcloud sql instances patch $CSQL_NAME \
--authorized-networks=$(gcloud compute instances describe $STRIIMVM_NAME \
--format='get(networkInterfaces[0].accessConfigs[0].natIP)' \
--zone=$STRIIMVM_ZONE)
```
Replace the following:
- `STRIIM_VM_NAME`: the name of the VM that you deployed with Striim
8. In the Google Cloud console, on the deployment instance details page,
click **Visit the site** to open the Striim web UI.
9. In the Striim configuration wizard, configure the following:
1. Review the end user license agreement. If you accept the terms, click **Accept Striim EULA and Continue**.
2. Enter your contact information.
3. Enter the Cluster Name, Admin, Sys, and Striim Key passwords of your choice. Make a note of these passwords.
4. Click **Save and Continue**.
5. Leave the key field blank to enable the trial, and then click **Save and Continue**.
10. Click **Launch** . It takes about a minute for Striim to be configured.
When done, click **Log In**.
11. To log in to the Striim administrator console, log in with the `admin` user
and the administrator password that you previously set. Keep this window
open because you return to it in a later step.
## Set up MySQL Connector/J
Use
[MySQL Connector/J](https://dev.mysql.com/downloads/connector/j/5.1.html)
to connect Striim to your Cloud SQL for MySQL instance. As of this writing,
5.1.49 is the latest version of Connector/J.
1. in the Google Cloud console, go to the **Deployments** page.
[Go to Deployments page](https://console.cloud.google.com/dm/deployments)
2. For the Striim instance, click **SSH** to automatically connect to the
instance.
3. Download the Connector/J to the instance and extract the contents of the
file:
```
wget https://dev.mysql.com/get/Downloads/Connector-J/mysql-connector-java-5.1.49.tar.gz
tar -xvzf mysql-connector-java-5.1.49.tar.gz
```
4. Copy the file to the Striim library path, allow it to be executable,
and change ownership of the file that you downloaded:
```
sudo cp ~/mysql-connector-java-5.1.49/mysql-connector-java-5.1.49.jar /opt/striim/lib
sudo chmod +x /opt/striim/lib/mysql-connector-java-5.1.49.jar
sudo chown striim /opt/striim/lib/mysql-connector-java-5.1.49.jar
```
5. To recognize the new library, restart the Striim server:
sudo systemctl stop striim-node
sudo systemctl stop striim-dbms
sudo systemctl start striim-dbms
sudo systemctl start striim-node
6. Go back to the browser window with the administration console in it.
Reload the page, and then log in using the `admin` user credentials.
It can take a couple minutes for the server to complete its restart from the
previous step, so you might get a browser error during that time. If you
encounter an error, reload the page and log in again.
## Load sample transactions to Cloud SQL
Before you can configure your first Striim app, load transactions into
the Cloud SQL for MySQL instance.
1. In Cloud Shell, connect to the instance using the
Cloud SQL for MySQL instance credentials that you previously set:
gcloud sql connect $CSQL_NAME --user=$CSQL_USERNAME
2. Create a sample database and load some sample transactions into it:
CREATE DATABASE striimdemo;
USE striimdemo;
CREATE TABLE ORDERS (ORDER_ID Integer, ORDER_DATE VARCHAR(50), ORDER_MODE VARCHAR(8), CUSTOMER_ID Integer, ORDER_STATUS Integer, ORDER_TOTAL Float, SALES_REP_ID Integer, PROMOTION_ID Integer, PRIMARY KEY (ORDER_ID));
INSERT INTO ORDERS (ORDER_ID, ORDER_DATE, ORDER_MODE, CUSTOMER_ID, ORDER_STATUS, ORDER_TOTAL, SALES_REP_ID, PROMOTION_ID) VALUES (1001, 1568927976017, 'In-Store', 1001, 9, 34672.59, 331, 9404);
INSERT INTO ORDERS (ORDER_ID, ORDER_DATE, ORDER_MODE, CUSTOMER_ID, ORDER_STATUS, ORDER_TOTAL, SALES_REP_ID, PROMOTION_ID) VALUES (1002, 1568928036017, 'In-Store', 1002, 1, 28133.14, 619, 2689);
INSERT INTO ORDERS (ORDER_ID, ORDER_DATE, ORDER_MODE, CUSTOMER_ID, ORDER_STATUS, ORDER_TOTAL, SALES_REP_ID, PROMOTION_ID) VALUES (1003, 1568928096017, 'CompanyB', 1003, 1, 37367.95, 160, 30888);
INSERT INTO ORDERS (ORDER_ID, ORDER_DATE, ORDER_MODE, CUSTOMER_ID, ORDER_STATUS, ORDER_TOTAL, SALES_REP_ID, PROMOTION_ID) VALUES (1004, 1568928156017, 'CompanyA', 1004, 1, 7737.02, 362, 89488);
INSERT INTO ORDERS (ORDER_ID, ORDER_DATE, ORDER_MODE, CUSTOMER_ID, ORDER_STATUS, ORDER_TOTAL, SALES_REP_ID, PROMOTION_ID) VALUES (1005, 1568928216017, 'CompanyA', 1005, 9, 15959.91, 497, 78454);
INSERT INTO ORDERS (ORDER_ID, ORDER_DATE, ORDER_MODE, CUSTOMER_ID, ORDER_STATUS, ORDER_TOTAL, SALES_REP_ID, PROMOTION_ID) VALUES (1006, 1568928276017, 'In-Store', 1006, 1, 82531.55, 399, 22488);
INSERT INTO ORDERS (ORDER_ID, ORDER_DATE, ORDER_MODE, CUSTOMER_ID, ORDER_STATUS, ORDER_TOTAL, SALES_REP_ID, PROMOTION_ID) VALUES (1007, 1568928336017, 'CompanyA', 1007, 7, 52929.61, 420, 66256);
INSERT INTO ORDERS (ORDER_ID, ORDER_DATE, ORDER_MODE, CUSTOMER_ID, ORDER_STATUS, ORDER_TOTAL, SALES_REP_ID, PROMOTION_ID) VALUES (1008, 1568928396017, 'Online', 1008, 1, 26912.56, 832, 7262);
INSERT INTO ORDERS (ORDER_ID, ORDER_DATE, ORDER_MODE, CUSTOMER_ID, ORDER_STATUS, ORDER_TOTAL, SALES_REP_ID, PROMOTION_ID) VALUES (1009, 1568928456017, 'CompanyA', 1009, 1, 97706.08, 124, 12185);
INSERT INTO ORDERS (ORDER_ID, ORDER_DATE, ORDER_MODE, CUSTOMER_ID, ORDER_STATUS, ORDER_TOTAL, SALES_REP_ID, PROMOTION_ID) VALUES (1010, 1568928516017, 'CompanyB', 1010, 1, 47539.16, 105, 17868);
3. To check the upload, count the records to ensure that 10 records were
inserted:
SELECT COUNT(*) FROM ORDERS;
4. Leave the Cloud SQL for MySQL instance:
```
Exit
```
## Create a Spanner target instance
In this section, you create a Spanner instance and load service account
credentials so that Striim can write to the target instance from the
Google Cloud console.
1. In Cloud Shell, create a Spanner instance:
gcloud spanner instances create striim-spanner-demo \
--config=regional-us-central1 --nodes=1 \
--description="Test Target for Striim"
For this tutorial, deploy Spanner in the same region as
Cloud SQL. If you chose a different region than `us-central1`,
change the region. For more information about Spanner and regions,
see
[instances](https://docs.cloud.google.com/spanner/docs/instances).
2. Create a database in the new instance with the target table:
gcloud spanner databases create striimdemo \
--instance=striim-spanner-demo \
--ddl="CREATE TABLE orders (ORDER_ID INT64,ORDER_DATE STRING(MAX),ORDER_MODE STRING(MAX),CUSTOMER_ID INT64,ORDER_STATUS INT64,ORDER_TOTAL FLOAT64,SALES_REP_ID INT64,PROMOTION_ID INT64) PRIMARY KEY (ORDER_ID)"
3. Create a service account for Striim to connect to Spanner:
gcloud iam service-accounts create striim-spanner \
--display-name striim-spanner
export sa_striim_spanner=$(gcloud iam service-accounts list \
--filter="displayName:striim-spanner" --format='value(email)')
export PROJECT=$(gcloud info \
--format='value(config.project)')
gcloud projects add-iam-policy-binding $PROJECT \
--role roles/spanner.databaseUser \
--member serviceAccount:$sa_striim_spanner
gcloud iam service-accounts keys create ~/striim-spanner-key.json \
--iam-account $sa_striim_spanner
A key called `striim-spanner-key.json` is created in your home path.
4. Move the newly generated key to the server:
```
gcloud compute scp ~/striim-spanner-key.json $STRIIMVM_NAME:~ \
--zone=$STRIIMVM_ZONE
gcloud compute ssh --zone=$STRIIMVM_ZONE $STRIIMVM_NAME \
-- 'sudo cp ~/striim-spanner-key.json /opt/striim && \
sudo chown striim /opt/striim/striim-spanner-key.json'
```
You are now ready to create a Striim app.
## Create an online database migration
An online database migration moves data from a source database (either
on-premises or hosted on a cloud provider) to a target database in
Google Cloud. The source database remains fully accessible by the business
app and with minimal performance impact on the source database during this
time.
In an online migration, you perform an initial bulk load, and also continuously
capture any changes. You then synchronize the two databases to ensure that data
isn't lost. Typically both databases are retained for long periods of time to
test and verify that the app and users aren't impacted by switching to a new
cloud database.
### Create the source connection
1. In the Google Cloud console, on the instance details page, click **Visit the site** to open the Striim web UI.
2. In the Striim web UI, click **Apps**.
3. Click **Add App**.
4. Click **Start from Scratch**.
5. In the **Name** field, enter `demo_online`.
6. In the **Namespace** drop-down menu, select the default **Admin
namespace**. This label is used to organize your apps.
7. Click **Save**.
8. On the **Flow Designer** page, to do a one-time bulk initial load of
data, from the **Sources** pane, drag **Database** to the flow design
palette in the center of the screen and enter the following connection
properties:
- In the **Name** field, enter `mysql_source`.
- Leave the **Adapter** field at the default value of **DatabaseReader**.
- In the **Connection URL** field, enter
`jdbc:mysql://PRIMARY_ADDRESS:3306/striimdemo`.
Replace
`PRIMARY_ADDRESS` with the IP address of the
Cloud SQL instance that you created in the
[previous section](https://docs.cloud.google.com/architecture/partners/continuous-data-replication-cloud-spanner-striim#create_a_cloud_sql_for_mysql_instance).
- In the **Username** field, enter the username that you set as
the `CSQL_USER` environment variable, `striim-user`.
- In the **Password** field, enter the `CSQL_USER_PWD` value that
you made a note of when you
[created a Cloud SQL for MySQL instance](https://docs.cloud.google.com/architecture/partners/continuous-data-replication-cloud-spanner-striim#create_a_cloud_sql_for_mysql_instance).
- To see more configuration properties, click **Show optional
properties**.
- In the **Tables** field, enter `striimdemo.ORDERS`.
- For **Output to** , select **New output.**
- In the **New output** field, enter `stream_CloudSQLMySQLInitLoad`.
- Click **Save**.
9. To test the configuration settings to make sure that Striim can
successfully connect to Cloud SQL for MySQL, click **Created** , and
then select **Deploy App**.
10. In the **Deployment** window, you can specify that you want to run
parts of your app on some of your deployment topology. For this tutorial,
select **Default** , and click **Deploy**.
11. To preview your data as it flows through the Striim pipeline, click
**`mysql_source DataBase reader`** , and then click
**Preview on run**.
12. Click **Deployed** , and then click **Start App**.
The Striim app starts running, and data flows through the pipeline. If there
are any errors,
there is an issue connecting to the source database because there is only a
source component in the pipeline. If you see your app successfully run, but
no data flows through, typically that means that you don't have any
data in your database.
13. After you've successfully connected to your source database and tested
that it can read data, click **Running** , and then select **Stop App**.
14. Click **Stopped** , and then select **Undeploy App**. You are now ready
to connect this flow to Spanner.
### Perform an initial load into Spanner
1. In the Striim web UI, click **`mysql_source Database reader`**.
2. Click
**Connect to next component** , select **Connect next
Target component**, and then complete the following fields:
- In the **Name** field, enter `tgt_online_spanner`.
- In the **Adapter** field, enter `SpannerWriter`.
- In the **Instance ID** field, enter `striim-spanner-demo`.
- The **Tables property** is a source/target pair separated by
commas. It is in the format of `srcSchema1.srcTable1,tgtSchema1.tgtTable1;srcSchema2.srcTable2,tgtSchema2.tgtTable2`.
For this tutorial, enter `striimdemo.ORDERS,striimdemo.orders`.
- The **Service Account Key** requires a fully qualified path and
name of the key file that was previously generated. For this tutorial,
enter `/opt/striim/striim-spanner-key.json`.
3. Click **Save**.
4. To deploy the app and preview the data flow, do the following:
- Click **Created** , and then select **Deploy App**.
- In the **Deployment** window, select **Default** , and then click **Deploy**.
- To preview your data as it flows through the Striim pipeline, click **`mysql_source Database reader`** , and then click **Preview on run**.
- Click **Deployed** , and then click **Start App**.
5. In the Google Cloud console, go to the **Spanner** page.
[Go to Spanner](https://console.cloud.google.com/spanner/instances)
6. Click the **`striimdemo`** database.
7. In the query editor, enter `SELECT * from orders LIMIT 100,` and then
click **Run**. The results table outputs the replicated data.
You have successfully set up your Striim environment and pipeline to
perform a batch load.
## Create a continuous data pipeline from Cloud SQL for MySQL to Spanner
With an initial one-time bulk load in place, you can now set up a continuous
replication pipeline. This pipeline is similar to the bulk pipeline that you
just created, but with a different source object.
### Create a CDC source
1. In the Striim web UI, click **Home**.
2. Click **Apps**.
3. Click **Start from Scratch**.
4. In the **Name** field, enter `MySQLToCloudSpanner_cdc`.
5. In the **Namespace** drop-down menu, select **Admin namespace**.
6. On the **Flow Designer** page, drag a **MySQL CDC** source reader to the center of the design palette.
7. Configure your new MySQL CDC source with the following information:
- In the **Name** field, enter `mysql_cdc_source`.
- Leave the **Adapter** field at the default value of **MysqlReader**.
- In the **Connection URL** field, enter `jdbc:mysql://PRIMARY_ADDRESS:3306/striimdemo`.
- Enter the username and password that you used in the previous section.
- To see more configuration properties, click **Show optional
properties**.
- In the **Tables** field, enter `striimdemo.ORDERS`.
- For **Output to** , select **New output**.
- In the **New output** field, enter `tgt_MySQLCDCSpanner`.
- Click **Save**.
### Load new transactions into Spanner
1. Click **MysqlReader**.
2. Click
**Connect to next component** , and then select **Connect next
Target component**.
- In the **Name** field, enter `tgt_cdc_spanner`.
- In the **Adapter** field, enter `SpannerWriter`.
- In the **Instance ID** field, enter `striim-spanner-demo`.
- The **Tables property** is a source/target pair separated by
commas. It is in the format of `srcSchema1.srcTable1,tgtSchema1.tgtTable1;srcSchema2.srcTable2,tgtSchema2.tgtTable2`.
For this tutorial, use `striimdemo.ORDERS,striimdemo.orders`.
- The **Service Account Key** requires a fully qualified path and
name of the key file that was previously generated. For this tutorial,
enter `/opt/striim/striim-spanner-key.json`.
3. Click **Save**.
4. To deploy the app and preview the data flow, do the following:
- Click **Created** , and then select **Deploy App**.
- In the **Deployment** window, select **Default** , and then click **Deploy**.
- To preview your data as it flows through the Striim pipeline, click **MysqlReader** , and then click **Preview on Run**.
- Click **Deployed** , and then click **Start App**.
5. In Cloud Shell, connect to your Cloud SQL for MySQL instance:
gcloud sql connect $CSQL_NAME --user=$CSQL_USERNAME
6. Tell MySQL to use this database where the `ORDERS` table lives:
USE striimdemo;
INSERT INTO ORDERS (ORDER_ID, ORDER_DATE, ORDER_MODE, CUSTOMER_ID, ORDER_STATUS, ORDER_TOTAL, SALES_REP_ID, PROMOTION_ID) VALUES (1011, 1568928576017, 'In-Store', 1011, 9, 13879.56, 320, 88252);
INSERT INTO ORDERS (ORDER_ID, ORDER_DATE, ORDER_MODE, CUSTOMER_ID, ORDER_STATUS, ORDER_TOTAL, SALES_REP_ID, PROMOTION_ID) VALUES (1012, 1568928636017, 'CompanyA', 1012, 1, 19729.99, 76, 95203);
INSERT INTO ORDERS (ORDER_ID, ORDER_DATE, ORDER_MODE, CUSTOMER_ID, ORDER_STATUS, ORDER_TOTAL, SALES_REP_ID, PROMOTION_ID) VALUES (1013, 1568928696017, 'In-Store', 1013, 5, 7286.68, 164, 45162);
INSERT INTO ORDERS (ORDER_ID, ORDER_DATE, ORDER_MODE, CUSTOMER_ID, ORDER_STATUS, ORDER_TOTAL, SALES_REP_ID, PROMOTION_ID) VALUES (1014, 1568928756017, 'Online', 1014, 1, 87268.61, 909, 70407);
INSERT INTO ORDERS (ORDER_ID, ORDER_DATE, ORDER_MODE, CUSTOMER_ID, ORDER_STATUS, ORDER_TOTAL, SALES_REP_ID, PROMOTION_ID) VALUES (1015, 1568928816017, 'CompanyB', 1015, 1, 69744.13, 424, 79401);
In the Striim web UI, on the **Transactions view** page, transactions
now populate the page and show that data is flowing.
7. In the Google Cloud console, go to the **Spanner** page.
[Go to Spanner](https://console.cloud.google.com/spanner/instances)
8. To see that the data is successfully replicated to the target, click the
**`striimdemo`** database, and then click the **Orders** table. Click the
**Data** tab and you now see that these transactions have successfully
replicated to the target.
You have successfully set up a streaming pipeline from
Cloud SQL for MySQL to Spanner.
## Clean up
The easiest way to eliminate billing is to delete the Google Cloud project you created for the tutorial. Alternatively, you can delete the individual resources.
### Delete the project
> [!CAUTION]
> **Caution** : Deleting a project has the following effects:
>
> - **Everything in the project is deleted.** If you used an existing project for the tasks in this document, when you delete it, you also delete any other work you've done in the project.
> - **Custom project IDs are lost.** When you created this project, you might have created a custom project ID that you want to use in the future. To preserve the URLs that use the project ID, such as an `appspot.com` URL, delete selected resources inside the project instead of deleting the whole project.
1. In the Google Cloud console, go to the **Manage resources** page.
[Go to Manage resources](https://console.cloud.google.com/iam-admin/projects)
2. In the project list, select the project that you want to delete, and then click **Delete**.
3. In the dialog, type the project ID, and then click **Shut down** to delete the project.
## What's next
- Explore reference architectures, diagrams, and best practices about Google Cloud. Take a look at our [Cloud Architecture Center](https://docs.cloud.google.com/architecture).
- Take a look at [Google Cloud data migration](https://cloud.google.com/solutions/database-migration).
- If you want to learn more about Striim, [visit the Striim website](http://www.striim.com), [schedule a demo with a Striim technologist](https://go2.striim.com/demo-region-select), and subscribe to the [Striim blog](https://www.striim.com/blog).