CloudSQL MySQL snapshot

Release status Released Supported by Stitch
Availability Free Supported Versions n/a
SSL connections Unsupported VPN Connections Unsupported
Data selection Tables and columns View Replication Unsupported

Connecting CloudSQL MySQL

CloudSQL MySQL Setup Requirements

To set up CloudSQL MySQL in Stitch, you need:

  • The CREATE USER or INSERT privilege (for the mysql database). The CREATE USER privilege is required to create a database user for Stitch.

  • The GRANT OPTION privilege in CloudSQL MySQL. The GRANT OPTION privilege is required to grant the necessary privileges to the Stitch database user.

Step 1: Whitelist Stitch's IP addresses

For Stitch to successfully connect with your CloudSQL instance, you’ll need to add our IP addresses to the database’s authorized IP addresses list.

  1. Sign into your Google Cloud Platform account.
  2. Navigate to the Cloud SQL Instances page.
  3. Click the instance name to open its details page.
  4. Click the Authorization tab.
  5. For each of the following IP addresses, complete the following:

    1. Click Add network.
    2. In the Name field, enter a name for the IP address. For example: Stitch-1 for the first IP address, Stitch-2 for the second, and so on.
    3. In the Network field, paste one of the following IP addresses:





    4. Click Done.
    5. Repeat these steps until all of Stitch’s IP addresses have been added.
  6. When finished, click Save to update the instance.

Step 2: Configure database server settings

Step 2.1: Enable binary logging

Next, you need to verify that binary logging is enabled for your CloudSQL MySQL instance.

  1. On the Instance details page in Google Cloud Platform, click the Edit option at the top of the page.
  2. In the Configuration options section, open Enable auto backups.
  3. If unchecked, check the Enable binary logging option.
  4. Click Save.

Step 2.2: Define database parameters

Next, you’ll configure your server to use Log-based Incremental Replication, or binlog replication.

Log-based Incremental Replication is a method of replication that reads a database’s binary log files. These files contain information about modifications made to data in a CloudSQL MySQL instance. Log-based Incremental Replication captures all inserts, updates, and deletes made to records during each replication job, and is the most accurate and efficient method of replication.

While Stitch recommends using Log-based Replication to replicate data, it isn’t mandatory. Stitch offers additional Replication Methods for CloudSQL MySQL databases that don’t require defining these settings.

  1. Log into your CloudSQL MySQL server.
  2. Verify that binlog is enabled by running the following statement. The value returned should be 1:

    mysql> select @@log_bin;

    If this statement returns a 0, this means that binlog is disabled. You’ll enable it in the next step.

  3. Locate the my.cnf file, usually located at /etc/my.cnf. Verify that my.cnf has the following lines in the mysqld section:


    A few things to note:

    • log_bin doesn’t have to be mysql-binlog - this value can be anything. Additionally, if log_bin already has an entry (which you checked in step one), you don’t need to change it.
    • Use either expire_log_days or binlog_expire_logs_seconds, not both. See the Server settings list tab for more information.
    • Setting log_slave_updates is only required if you are connecting a read replica. This isn’t required for master instances.
  4. When finished, restart your CloudSQL MySQL server to ensure the changes take effect.

In the table below are the names, required values, and descriptions of the server settings you must define.

Setting Value Description
binlog_format ROW

Note: This setting is available on CloudSQL MySQL databases running version 5.6.2 or greater.

Defines the binary logging format. A ROW value enables “event-based” capture, which describes what happens to records in the database. This is necessary to use binlog.

Stitch supports the following event types:

binlog_row_image FULL

Note: This setting is available on CloudSQL MySQL databases running version 5.6.2 or greater.

Defines how row images are written to the binary log. A FULL value ensures that all columns in a row are logged in the before and after images of a change, enabling Stitch to accurately capture all changes made to a record.

expire_logs_days 7

Specifies the amount of time, in days, before the automatic removal of binary log files. Stitch recommends a retention period of 7 days, but a minimum of 3 days will also work.

Do not use both expire_logs_days and binlog_expire_logs_seconds - only define one. The value of this variable will be ignored if binlog_expire_logs_seconds also contains a value.

Note: This variable is deprecated as of MySQL version 8.0.3, and will be removed in a future release. If using MySQL versions 8.0.1+, use binlog_expire_logs_seconds instead.

binlog_expire_logs_seconds 604800

Specifies the amount of time, in seconds, before the automatic removal of binary log files. Stitch recommends a retention period of 7 days, but a minimum of 3 days will also work.

Note: This variable is available on MySQL versions 8.0.1+.

log_bin mysql-binlog

Acts as the “on” switch for binary logging. This is the name of the binary logging file on the database server. For example: mysql-binlog

Note: The name of this file doesn’t have to be mysql-binlog. If your server already specifies a log-bin entry, there’s no need to change it.

Step 3: Create a Stitch database user

Next, you’ll create a dedicated database user for Stitch. This will ensure Stitch is visible in any logs or audits, and allow you to maintain your privilege hierarchy.

To create a database user for Stitch, run the following command when logged into CloudSQL MySQL:

CREATE USER '[stitch_username]'@'localhost' IDENTIFIED BY '[password]';

Replace [password] with a secure password.

If you wish to restrict this user from accessing data in specific databases, tables, or columns, you can instead run GRANT queries that only allow access to the data you permit.

See the Privileges list tab for an explanation of why these permissions are required by Stitch.

In the table below are the database user privileges Stitch requires to connect to and replicate data from a CloudSQL MySQL database.

Privilege name Reason for requirement

Required to select rows from tables in a database.


Required for binlog replication. Required to use SHOW BINARY LOGS, which determines that a binary log exists.


Required for binlog replication. Required to use SHOW MASTER STATUS, which fetches the current binlog file and position on the server.

Step 4: Retrieve server IDs

When Stitch connects to your database and uses Log-based Replication, a unique server ID will be required. This ID ensures that the integration - or integrations, if you’re connecting multiple databases - will not encounter conflicts during the replication process.

To avoid conflicts, you’ll check which server IDs are currently in use and then define a new, unqiue ID in Stitch.

  1. Log into the MySQL server that acts as the replication master.
  2. Run the following statement:

    mysql> SHOW SLAVE HOSTS;
  3. The SHOW SLAVE HOSTS statement will return information about servers that are or have been connected as replication slaves:

    | Server_id  | Host        | Port | Master_id | Slave_UUID |
    | 192168010  | stitch_prod | 3306 | 192168011 | <UUID>     |
    | 1921680101 | stitch_dev  | 3306 | 192168011 | <UUID>     |

In the next step, you’ll define a unique server ID for your Stitch CloudSQL MySQL integration to use.

Step 5: Connect Stitch

  1. Sign into your Stitch account, if you haven’t already.
  2. On the Stitch Dashboard page, click the Add Integration button.
  3. Click the CloudSQL MySQL icon.
  4. Fill in the fields as follows:

    • Integration Name: Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your data warehouse.

      For example, the name “Stitch CloudSQL MySQL” would create a schema called stitch_cloudsql_mysql in the data warehouse. Note: The schema name cannot be changed after the integration is saved.

    • Host (Endpoint): Enter the host address (endpoint) of your CloudSQL MySQL instance. This will be the value of the Primary IPv4 address that you retrieved in step 2.

    • Port: Enter the port used by the CloudSQL MySQL instance. The default is 3306.

    • Username: Enter the Stitch CloudSQL MySQL database user’s username.

    • Password: Enter the password for the Stitch database user.

    • Database: Optional: Enter the name of the default database Stitch will connect to. Stitch will ‘find’ all databases you give the Stitch user access to - a default database is only used to test and complete the connection.

    • Server ID: Optional: Enter the unique server ID of instance you’re connecting to Stitch.

      This can be any numeric value within MySQL’s accepted server ID range, as long as it’s unique to the instance. For example: If in the Retrieve Server IDs step there are servers with the IDs 192168010 and 1921680101, you can enter any other numbers in this field.

Step 6: Create a replication schedule

In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

Stitch offers two methods of creating a replication schedule:

  • Replication Frequency: This method requires selecting the interval you want replication to run for the integration. Start times of replication jobs are based on the start time and duration of the previous job. Refer to the Replication Frequency documentation for more information and examples.
  • Anchor scheduling: Based on the Replication Frequency, or interval, you select, this method “anchors” the start times of this integration’s replication jobs to a time you select to create a predictable schedule. Anchor scheduling is a combination of the Anchor Time and Replication Frequency settings, which must both be defined to use this method. Additionally, note that:

    • A Replication Frequency of at least one hour is required to use anchor scheduling.
    • An initial replication job may not begin immediately after saving the integration, depending on the selected Replication Frequency and Anchor Time. Refer to the Anchor Scheduling documentation for more information.

    • You’ll need to contact support to request using an Anchor Time with this integration.

To help prevent overages, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.

Step 7: Select data to replicate

The last step is to select the tables and columns you want to replicate. When you track a table, you’ll also need to define its Replication Method and, if using Key-based Incremental Replication, its Replication Key.

You can track tables and columns by:

  1. In the Integration Details page, click the Tables to Replicate tab.
  2. Locate a table you want to replicate.
  3. Click the checkbox next to the object’s name. A green checkmark means the object is set to replicate.
  4. If there are child objects, they’ll automatically display and you’ll be prompted to select some.
  5. After you set a table to replicate, the Table Settings page will display. Note: When you track a table, by default all columns will also be tracked.
  6. In the Table Settings page, define the table’s Replication Method and, if using Key-based Incremental Replication, its Replication Key.

  7. Repeat this process for every table you want to replicate.

  8. Click the Finalize Your Selections button to save your data selections.

Initial and historical replication jobs

After you finish setting up CloudSQL MySQL, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial replication job for the integration. This may take some time to complete.

Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.

Extracting data from CloudSQL MySQL

When you connect a database as an input, Stitch only needs read-only access to the databases, tables, and columns you want to replicate. There are two processes Stitch runs during the Extraction phase of the replication process: a structure sync and a data sync.

Structure syncs

This is the first part of the Extraction process. During this phase, Stitch will detect any changes to the structure of your database. For example: A new column is added to one of the tables you set to replicate in Stitch. Structure syncs are how Stitch identifies the databases, tables, and columns to display in the Stitch app.

Stitch runs the following queries on CloudSQL MySQL databases to perform a structure sync:

  • SHOW TABLES FROM [database_name]
  • SHOW KEYS FROM [table_name]

Data syncs

This is the second part of the Extraction process. During this phase, Stitch extracts data from the source and replicates it. The method Stitch uses is the same for all databases, but differs depending on the Replication Method that each table uses.

The tabs below contain info about the queries Stitch runs during the data syncs for each type of Replication Method supported for CloudSQL MySQL integrations.

Data syncs for tables using Key-based Incremental

Initial (historical) replication jobs

During the initial replication job for a table using Key-based Incremental Replication, Stitch will replicate the table in full by running a SELECT query and read out of the resulting cursor in batches:

  SELECT column_a, column_b <,...>
    FROM table_a
ORDER BY replication_key_column
Ongoing replication jobs

During subsequent jobs, Stitch will use the last saved maximum value of the Replication Key column to identify new and updated data.

Stitch will run the following query and read out of the associated cursor in batches:

  SELECT column_a, column_b <,...>
    FROM table_a
   WHERE replication_key_column >= 'last_maximum_replication_key_value'
ORDER BY replication_key_column

Data syncs for tables using Log-based Incremental

Initial (historical) replication jobs

During the initial replication job for a table using Log-based Incremental Replication, Stitch will use a SELECT query to retrieve all data for the table and then read out of the resulting cursor in batches:

SELECT column_a, column_b <,...>
  FROM table_a
Ongoing replication jobs

During subsequent jobs, Stitch will use the database's binary logs to stream updates.

Stitch will 'bookmark' its position in the binary log at the end of each replication job, allowing it to resume at the correct position during the next extraction.

Data syncs for tables using Full Table

For tables using Full Table Replication, Stitch runs a single query and reads out of the resulting cursor in batches:

SELECT column_a, column_b <,...>
  FROM table_a

This query will be run for each table using Full Table Replication during every replication job, whether it's the initial historical job or a subsequent job.


While we make every effort to ensure the queries that Stitch executes don’t impart significant load on your databases, we still have some recommendations for guaranteeing database performance:

  • Use a replica database instead of connecting directly. We recommend using read replicas in lieu of directly connecting production databases with high availability and performance requirements.
  • Apply indexes to Replication Key columns. We restrict and order our replication queries by this column, so applying an index to the columns you’re using as Replication Keys can improve performance.

Questions? Feedback?

Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.