# MySQL (HP) (v2)

Information note **MySQL extraction is supported by Stitch**   
This integration is powered by [Singer's](https://www.singer.io/) MySQL tap and certified by Stitch.   
  
For support, contact [Support](https://community.qlik.com/t5/Support/ct-p/qlikSupport).

Information note **Keep up with the latest MySQL updates** with the [MySQL Integration Changelog](https://help.qlik.com/en-US/stitch/integrations/databases/mysql/changelog).

## MySQL integration summary

This version (v2) of Stitch’s MySQL integration optimizes replication by utilizing Avro schemas to write and validate data, thereby reducing the amount of time spent on data extraction and preparation. Compared to previous versions of the MySQL integration, this version boasts increased performance and overall reduced replication time.

Notable improvements and changes in this version also include:

* **New column (field) naming rules.** Avro has specific rules that dictate how columns can be named. As a result, column names will be canonicalized to adhere to Avro rules and persisted to your destination using the Avro-friendly name. Refer to the [Column name transformations section](https://help.qlik.com/en-US/stitch/integrations/databases/mysql/v2#data-replication--column-name-transformations) for more info.
* **Improved handling of `JSON` data types**. In previous versions, these data types were treated as strings. This version will send them to your destination as JSON objects, which may result in [de-nesting](https://help.qlik.com/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures).

To get a look at how this version compares to the previous version of MySQL, refer to the [MySQL version comparison documentation](https://help.qlik.com/en-US/stitch/integrations/databases/mysql#supported-features).

## MySQL feature snapshot

A high-level look at Stitch's MySQL (v2) integration, including release status, useful links, and the features supported in Stitch.

| **STITCH** |  |  |  |
| --- | --- | --- | --- |
| **[Release status](https://help.qlik.com/en-US/stitch/integrations/identify-an-integration-version)** | Released on November 8, 2021 | **Supported by**<br><br>the Info icon<br><br>Indicates if the integration is supported by Stitch or the Singer community. | [Stitch](https://community.qlik.com/t5/Support/ct-p/qlikSupport) |
| **Stitch plan**<br><br>the Info icon<br><br>The type of Stitch plan required to use the integration. | Standard | **Supported versions**<br><br>the Info icon<br><br>Indicates if the integration is supported by Stitch or the Singer community. | 5.6 and later |
| **[API availability](https://help.qlik.com/en-US/stitch/developers/stitch-connect/guides/source-destination-reference)**<br><br>the Info icon<br><br>Indicates if the integration is available as a source in Stitch Connect. | the Success icon<br><br>This version of the integration is available via the API.<br><br><br>Available | **Singer GitHub repository** | [](https://help.qlik.com/en-US/stitch/integrations/databases/mysql/v2) |
| **CONNECTION METHODS** |  |  |  |
| **SSH connections**<br><br>the Info icon<br><br>Indicates if SSH tunnels are supported for connecting this database to Stitch. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported | **SSL connections**<br><br>the Info icon<br><br>Indicates if SSL connections are supported for connecting this database to Stitch. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported |
| **REPLICATION SETTINGS** |  |  |  |
| **[Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/anchor-scheduling)**<br><br>the Info icon<br><br>A type of replication scheduling where an integration's Replication Frequency is anchored to a time you select. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported | **[Advanced Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/advanced-scheduling)**<br><br>the Info icon<br><br>A type of replication scheduling that allows you to specify granular start times for data extraction using cron expressions. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported |
| **Table-level reset**<br><br>the Info icon<br><br>Indicates if data can be reset at the table level. If unsupported, data can only be reset at the integration level. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported | **[Configurable Replication Methods](https://help.qlik.com/en-US/stitch/replication/replication-methods)**<br><br>the Info icon<br><br>Indicates if Replication Methods can be defined by you for tables in the integration. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported |
| **REPLICATION METHODS** |  |  |  |
| **[Log-based Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental)**<br><br>the Info icon<br><br>Log-based Incremental Replication is a replication method in which Stitch identifies modifications to records - including inserts, updates, and deletes - using a database's binary log files. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported | **[Key-based Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/key-based-incremental)**<br><br>the Info icon<br><br>Key-based Incremental Replication is a replication method in which Stitch identifies new and updated data using a column called a Replication Key. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported |
| **[Full Table Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/full-table)**<br><br>the Info icon<br><br>Full Table Replication is a replication method in which all rows in a table - including new, updated, and existing - are replicated during every replication job. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported |  |  |
| **DATA SELECTION** |  |  |  |
| **Table selection**<br><br>the Info icon<br><br>The ability to select individual tables for replication in the Stitch interface. If table selection is unavailable, all tables and all the columns they contain will be set to replicate by default. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported | **Column selection**<br><br>the Info icon<br><br>The ability to select individual columns for replication in the Stitch interface. If column selection is unavailable, all columns will be set to replicate by default. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported |
| **[View replication](https://help.qlik.com/en-US/stitch/replication/replicating-database-views)**<br><br>the Info icon<br><br>Indicates if Stitch supports replicating views from this database integration. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported | **Select all**<br><br>the Info icon<br><br>Indicates if the integration supports selecting all available tables and columns. | the Warning 2 icon<br><br>Log-based Incremental Replication must be enabled and set as the default Replication Method to use the Select All feature.<br><br><br>Supported, with prerequisites |
| **TRANSPARENCY** |  |  |  |
| **[Extraction Logs](https://help.qlik.com/en-US/stitch/replication/extractions/integration-extraction-logs)**<br><br>the Info icon<br><br>Logs detailing the Extraction phase of the replication process for a given integration. Includes error info, should an error occur. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported | **[Loading Reports](https://help.qlik.com/en-US/stitch/replication/integration-loading-reports)**<br><br>the Info icon<br><br>Reports detailing the Loading phase of the replication process for a given integration. Includes the number of rows loaded for each table and error info, should an error occur. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported |

## Connecting MySQL

### MySQL setup requirements

To set up MySQL in Stitch, you need:

* **The `CREATE USER` or `INSERT` privilege (for the `mysql` database).** The [`CREATE USER` privilege](https://dev.mysql.com/doc/refman/8.0/en/create-user.html) is required to create a database user for Stitch.

* **The `GRANT OPTION` privilege in MySQL.** The [`GRANT OPTION` privilege](https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_grant-option) is required to grant the necessary privileges to the Stitch database user.

* **The `SUPER` privilege in MySQL.** If using binlog replication, the [`SUPER` privilege](https://dev.mysql.com/doc/refman/5.6/en/privileges-provided.html#priv_super) is required to define the appropriate server settings.

### Step 1: Verify your Stitch account's data pipeline region

First, you’ll log into Stitch and verify the data pipeline region your account is using. Later in this guide, you’ll need to grant Stitch access by whitelisting our IP addresses.

The IP addresses you’ll whitelist depend on the [**Data pipeline region** your account is in](https://help.qlik.com/en-US/stitch/security/supported-data-pipeline-regions).

1. [Sign into your Stitch account](https://app.stitchdata.com/), if you haven’t already.

2. Click **User menu (your icon) &gt; Edit User Settings** and locate the **Data pipeline region** section to verify your account’s region.

3. Locate the list of IP addresses for your region:

   * [North America region IP addresses](https://help.qlik.com/en-US/stitch/security/stitch-ip-addresses#north-america-ip-addresses)

   * [Europe region IP addresses](https://help.qlik.com/en-US/stitch/security/stitch-ip-addresses#europe-ip-addresses)

Keep this list handy - you’ll need it later.

### Step 2: Configure database connection settings

In this step, you’ll configure the database server to allow traffic from Stitch to access it. There are two ways to connect your database:

* **A direct connection** will work if your database is publicly accessible.
* **An SSH tunnel** is required if your database isn’t publicly accessible. This method uses a publicly accessible instance, or an SSH server, to act as an intermediary between Stitch and your database. The SSH server will forward traffic from Stitch through an encrypted tunnel to the private database.

Click the option you’re using below and follow the instructions.

I'm using an SSH tunnel to connect.

1. Follow the steps in the [Setting up an SSH Tunnel for a database connection guide](https://help.qlik.com/en-US/stitch/security/data-encryption/setting-up-ssh-tunnel-for-database-connection) to set up an SSH tunnel for MySQL.
2. Complete the steps in this guide after the SSH setup is complete.

#### I'm using a direct connection.

For the connection to be successful, you’ll need to configure your firewall to allow access from our IP addresses.

The IP addresses you’ll whitelist depend on the [**Data pipeline region** your account is in](https://help.qlik.com/en-US/stitch/security/supported-data-pipeline-regions).

1. [Sign into your Stitch account](https://app.stitchdata.com/), if you haven’t already.

2. Click **User menu (your icon) &gt; Edit User Settings** and locate the **Data pipeline region** section to verify your account’s region.

3. Locate the list of IP addresses for your region:

   * [North America region IP addresses](https://help.qlik.com/en-US/stitch/security/stitch-ip-addresses#north-america-ip-addresses)

   * [Europe region IP addresses](https://help.qlik.com/en-US/stitch/security/stitch-ip-addresses#europe-ip-addresses)

4. Whitelist the appropriate IP addresses.

### Step 3: Configure Log-based Incremental Replication

Information note **Note**: Skip this step if you’re not planning to use Log-based Incremental Replication. [Click to skip ahead](https://help.qlik.com/en-US/stitch/integrations/databases/mysql/v2#db-user).

Information note

**Important:** **Requirements for configuring binlog replication**

**To use binlog replication, your MySQL database must be running MySQL version 5.6.2 or greater**.

Additionally, setting up binlog replication requires rebooting your database to ensure parameter changes take effect. To minimize disruptions, we recommend performing the reboot during non-peak usage hours.

While Log-based Incremental Replication is the most accurate and efficient method of replication, using this replication method may, at times, require manual intervention or impact the source database’s performance. Refer to the [Log-based Incremental Replication documentation](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental) for more info.

You can also use one of Stitch’s other [Replication Methods](https://help.qlik.com/en-US/stitch/replication/replication-methods), which don’t require any database configuration. Replication Methods can be changed at any time.

* [Step 3.1: Configure server settings](https://help.qlik.com/en-US/stitch/integrations/databases/mysql/v2#configure-database-server-settings)

* [Step 3.2: Retrieve server IDs](https://help.qlik.com/en-US/stitch/integrations/databases/mysql/v2#server-id)

#### Step 3.1: Configure server settings

In this step, you’ll configure your MySQL server to use Log-based Incremental Replication.

* Instructions
* Server settings list

1. Log into your 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:

   ```
   [mysqld]
   binlog_format=ROW
   binlog_row_image=FULL
   expire_logs_days=7
   binlog_expire_logs_seconds=604800
   log_bin=mysql-binlog
   log_slave_updates=1
   ```

   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 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](https://dev.mysql.com/doc/refman/5.6/en/replication-options-binary-log.html#sysvar_binlog_format) | `ROW` | **Note**: This setting is available on MySQL databases running version 5.6.2 or greater.<br><br>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.**<br><br>Stitch supports the following event types:<br><br><ul> <li><code>INSERT</code></li> <li><code>UPDATE</code></li> <li><code>DELETE</code></li></ul> |
| [binlog_row_image](https://dev.mysql.com/doc/refman/5.6/en/replication-options-binary-log.html#sysvar_binlog_row_image) | `FULL` | **Note**: This setting is available on MySQL databases running version 5.6.2 or greater.<br><br>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](https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_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.<br><br>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.<br><br>**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](https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_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.<br><br>**Note**: This variable is available on MySQL versions 8.0.1+. |
| [log_bin](https://dev.mysql.com/doc/refman/5.6/en/replication-options-binary-log.html#sysvar_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`<br><br>**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. |
| [log_slave_updates](https://dev.mysql.com/doc/refman/5.6/en/replication-options-binary-log.html#sysvar_log_slave_updates) | `1` | Indicates whether updates received by a read replica from a master server should be logged to the replica’s own binary log.<br><br>**Note**: This is applicable when using a read replica. |

#### Step 3.2: Retrieve server IDs

Information note

**Required for Log-based Replication**

This step is required if using Log-based Replication and any of the following are true:

1. You’re connecting a read replica to Stitch
2. You’re connecting multiple databases to Stitch, all of which are on the same MySQL server. These can be read replicas, or databases on the master instance.
3. You’re adding a new MySQL Stitch integration, and the database is on the same server as other previously-connected databases.

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>     |
   +------------+-------------+------+-----------+------------+
   ```

When you complete the setup in Stitch, you’ll define a unique server ID for your Stitch MySQL integration to use.

### Step 4: Create a Stitch database user

Information note **Note**: You must have the `CREATE USER` and `GRANT OPTION` privileges to complete this step.

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.

* Instructions
* Privileges list

1. Log into your database as a user with `CREATE USER` and `GRANT OPTION` privileges.

2. Run the following command to create the Stitch database user:

   ```
   CREATE USER '<stitch_username>'@'localhost' IDENTIFIED BY '<password>';
   ```

   Replace `<password>` with a secure password. If using SSH, this can be different than the SSH password.

3. Grant the Stitch user `SELECT` privileges by running this command for every table you want to replicate:

   ```
   GRANT SELECT ON '<database_name>'.'<table_name>' to '<stitch_username>'@'localhost';
   ```

   Limiting access to only the tables you want to replicate ensures that the integration can complete discovery (a structure sync) in a timely manner. If you encounter issues in Stitch where tables aren’t displaying, try limiting the Stitch database user’s table access.

   **Note:** Column-level permissions are not supported for use with Log-based Incremental Replication. Restricting access to columns will cause replication issues.

Information note

**Important:** **Using Log-based Incremental Replication**

Additionally, if you want to use Log-based Incremental Replication, you’ll also need to grant the Stitch user replication privileges:

```
GRANT REPLICATION CLIENT, REPLICATION SLAVE ON *.* TO '<stitch_username>'@'localhost';
```

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 MySQL database.

| **Privilege name** | **Reason for requirement** |
| --- | --- |
| [SELECT](https://dev.mysql.com/doc/refman/5.5/en/privileges-provided.html#priv_select) | Required to select rows from tables in a database. |
| [REPLICATION CLIENT](https://dev.mysql.com/doc/refman/5.5/en/privileges-provided.html#priv_replication-client) | **Required for binlog replication.** Required to use [`SHOW BINARY LOGS`](https://dev.mysql.com/doc/refman/5.5/en/show-binary-logs.html), which determines that a binary log exists. |
| [REPLICATION SLAVE](https://dev.mysql.com/doc/refman/5.5/en/privileges-provided.html#priv_replication-slave) | **Required for binlog replication.** Required to use [`SHOW MASTER STATUS`](https://dev.mysql.com/doc/refman/5.5/en/show-binary-logs.html), which fetches the current binlog file and position on the server. |

### Step 5: Connect Stitch

In this step, you’ll complete the setup by entering the database’s connection details and defining replication settings in Stitch.

* [Step 5.1: Define the database connection details](https://help.qlik.com/en-US/stitch/integrations/databases/mysql/v2#define-connection-details)

* [Step 5.2: Define the SSH connection details](https://help.qlik.com/en-US/stitch/integrations/databases/mysql/v2#ssh-connection-details)

* [Step 5.3: Define the SSL connection details](https://help.qlik.com/en-US/stitch/integrations/databases/mysql/v2#ssl-connection-details)

* [Step 5.4: Select databases to discover](https://help.qlik.com/en-US/stitch/integrations/databases/mysql/v2#filter-databases)

* [Step 5.5: Define the Log-based Replication setting](https://help.qlik.com/en-US/stitch/integrations/databases/mysql/v2#define-default-replication-method)

* [Step 5.6: Create a replication schedule](https://help.qlik.com/en-US/stitch/integrations/databases/mysql/v2#create-replication-schedule)

* [Step 5.7: Save the integration](https://help.qlik.com/en-US/stitch/integrations/databases/mysql/v2#save-integration)

#### Step 5.1: Define the database connection details

1. If you aren’t signed into your Stitch account, [sign in now](https://app.stitchdata.com/).

2. On the Stitch Dashboard page, click the **Add Integration** button.

3. Locate and click the **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 destination.

     For example, the name “Stitch MySQL” would create a schema called `stitch_mysql` in the destination. **Note:** The schema name cannot be changed after the integration is saved.

   * **Host (Endpoint)**: Enter the host address (endpoint) used by the MySQL instance. For example: This could be a network address such as `192.68.0.1`, or a server endpoint like `dbname.hosting-provider.com`.

   * **Port**: Enter the port used by the MySQL instance. The default is `3306`.

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

   * **Password**: Enter the password for the Stitch MySQL database user.

   * **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](https://dev.mysql.com/doc/refman/8.0/en/replication-options.html), as long as it’s unique to the instance. For example: If in the [Retrieve Server IDs step](https://help.qlik.com/en-US/stitch/integrations/databases/mysql/v2#server-id) there are servers with the IDs `192168010` and `1921680101`, you can enter any other numbers in this field.

#### Step 5.2: Define the SSH connection details

Information note **Note**: Skip this step if you’re not using SSH to connect to Stitch.

If you’re using an SSH tunnel to connect your MySQL database to Stitch, you’ll also need to define the SSH settings. Refer to the [Setting up an SSH Tunnel for a database connection guide](https://help.qlik.com/en-US/stitch/security/data-encryption/setting-up-ssh-tunnel-for-database-connection) for assistance with completing these fields.

1. Click the **SSH Tunnel** checkbox.

2. Fill in the fields as follows:

   * **SSH Host**: Enter the public IP address or hostname of the server Stitch will SSH into.

   * **SSH Port**: Enter the SSH port on your server. (`22` by default)

   * **SSH User**: Enter the Stitch Linux (SSH) user’s username.

#### Step 5.3: Define the SSL connection details

Information note **Note**: Skip this step if you’re not using SSL to connect to Stitch.

1. Check the **Connect using SSL** checkbox. **Note:** The database must support and allow SSL connections for this setting to work correctly.

2. Fill in the fields as follows:

   * **SSL Certificate**: The certificate (typically a CA or server certificate) Stitch should verify the SSL connection against. The connection will succeed only if the server’s certifcate verifies against the certificate provided.

     **Note**: Providing a certifcate via this property isn’t required to use SSL. This is only if Stitch should verify the connection against a specific certificate.

   * **Use an SSL client key**: If SSL client authentication should be used, check this box. This will display the **Client Certificate** and **Client Key** fields, which are both required when using client authentication.

   * **Client Certificate**: If using SSL client authentication, paste the client certificate Stitch should use into this field. **Note**: You must also provide a **Client Key** for the connection to be successful.

   * **Client Key**: If using SSL client authentication, paste the client key Stitch should use into this field. **Note**: You must also provide a **Client Certificate** for the connection to be successful.

#### Step 5.4: Select databases to discover

Information note **Note**: Skip this step if you don’t need to filter databases.

Enter a database name in the field under **Filter databases in the source** to select the database that Stitch can discover. You can add multiple database names by clicking **Add another database**.

If no database is specified, Stitch will discover all databases on the host.

#### Step 5.5: Define the Log-based Replication setting

In the **Log-based Replication** section, you can set this as the integration’s default Replication Method.

When enabled, tables that are set to replicate will use [Log-based Incremental Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental) by default. If you don’t want a table to use Log-based Incremental Replication, you can change it in the Table Settings page for that table.

If this setting isn’t enabled, you’ll have to select a [Replication Method](https://help.qlik.com/en-US/stitch/integrations/databases/mysql/v2#sync-data) for each table you set to replicate.

#### Step 5.6: Create a replication schedule

Information note Replication schedules affect the time Extraction begins, not the time to data loaded. Refer to the [Replication Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling) documentation for more information.

In the **Replication Frequency** section, you’ll create the integration’s [replication schedule](https://help.qlik.com/en-US/stitch/replication/replication-scheduling). An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

MySQL integrations support the following replication scheduling methods:

* [Replication Frequency](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/replication-frequency)

* [Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/anchor-scheduling)

* [Advanced Scheduling using Cron](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/advanced-scheduling) (Advanced or Premium plans only)

To keep your row usage low, consider setting the integration to replicate less frequently. See the [Understanding and Reducing Your Row Usage guide](https://help.qlik.com/en-US/stitch/getting-started/understanding-stitch-usage) for tips on reducing your usage.

#### Step 5.7: Save the integration

When finished, click **Check and Save**.

Stitch will perform a connection test to the MySQL database; if successful, a *Success!* message will display at the top of the screen. **Note**: This test may take a few minutes to complete.

### Step 6: Select data to replicate

Information note **Is an object missing or not replicating?** Verify that the object meets the requirements for [selection](https://help.qlik.com/en-US/stitch/replication/extractions/data-selection/setting-tables-and-columns-to-replicate#selection-requirements) and [replication](https://help.qlik.com/en-US/stitch/replication/extractions/data-selection/setting-tables-and-columns-to-replicate#replication-requirements).

The last step is to select the tables and columns you want to replicate. [](https://help.qlik.com/en-US/stitch/integrations/databases/mysql/v2#schema)

**Note**: If a replication job is currently in progress, new selections won’t be used until the next job starts.

* Selection options
* Individual tables and columns
* All tables and columns
* Database views

For MySQL integrations, you can select:

1. **Individual tables and columns**

2. **All tables and columns** (except views)

3. **Database views**

Click the tabs to view instructions for each selection method.

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 table’s name. A blue checkmark means the table is set to replicate.

4. After you set a table to replicate, a page with the table’s columns will display. De-select columns if needed.

5. Next, you’ll define the table’s Replication Method. Click the **Table Settings** button.

6. In the **Table Settings** page:

   1. Define the table’s **Replication Method**, or skip this step if you want to use the [integration’s default method](https://help.qlik.com/en-US/stitch/integrations/databases/mysql/v2#define-log-based-replication-setting).

   2. If using [Key-based Incremental Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/key-based-incremental), select a [Replication Key](https://help.qlik.com/en-US/stitch/replication/replication-keys).

   3. When finished, click **Update Settings**.

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

8. Click the **Finalize Your Selections** button at the bottom of the page to save your data selections.

Information note

**Important:** Before using this feature, note that:

1. Using the **Select All** feature will overwrite any previous selections. However, selections aren’t final until **Finalize Your Selections** is clicked. Clicking **Cancel** will restore your previous selections.

2. Log-based Incremental Replication must be enabled and set as the default Replication Method to use the Select All feature.

Refer to the [Select All guide](https://help.qlik.com/en-US/stitch/replication/extractions/data-selection/setting-tables-and-columns-to-replicate#set-all-data-to-replicate) for more info about this feature.

1. Click into the integration from the Stitch Dashboard page.

2. Click the **Tables to Replicate** tab.

3. Navigate to the table level, selecting any databases and/or schemas that contain tables you want to replicate.

4. In the list of tables, click the box next to the **Table Names** column.

5. In the menu that displays, click **Track AllTables and Fields (Except Views)**:

   ![The Track AllTables and Fields (Except Views) menu in the Tables to Replicate tab](https://help.qlik.com/en-US/stitch/images/replication/select-all-tables-menu.png)The Track AllTables and Fields (Except Views) menu in the Tables to Replicate tabThe Track AllTables and Fields (Except Views) menu in the Tables to Replicate tab

6. Click the **Finalize Your Selections** button at the bottom of the page to save your data selections.

Setting a database view to replicate is similar to selecting a table, with a few differences. Refer to the [Replicating Database Views guide](https://help.qlik.com/en-US/stitch/replication/replicating-database-views) for detailed instructions.

At a high level, you’ll need to complete the following to select a database view:

1. [Verify the database user’s permissions](https://help.qlik.com/en-US/stitch/replication/replicating-database-views#step--verify-database-user-permissions)
2. [Select the view](https://help.qlik.com/en-US/stitch/replication/replicating-database-views#step--select-view-in-stitch)
3. **Optional**: [Define the view’s Primary Key](https://help.qlik.com/en-US/stitch/replication/replicating-database-views#step--define-view-primary-key)
4. [Define the view’s Replication Method](https://help.qlik.com/en-US/stitch/replication/replicating-database-views#step--define-view-replication-method)
5. [Save the view’s settings](https://help.qlik.com/en-US/stitch/replication/replicating-database-views#step--save-view-settings)

### Initial and historical replication jobs

After you finish setting up 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.**

Information note

**Initial replication jobs with Anchor Scheduling**

If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to the [Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling#job-scheduling-and-anchor-times) documentation for more information.

#### 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.

Information note **Replication will continue after the seven days are over**. If you’re no longer interested in this source, be sure to **pause** or **delete** the integration to prevent unwanted usage.

## MySQL replication

In this section:

* [Details about Extraction, including object and data type discovery and selecting data for replication](https://help.qlik.com/en-US/stitch/integrations/databases/mysql/v2#extraction-details)

### Extraction

For every table set to replicate, Stitch will perform the following during Extraction:

* [Discover table schemas and type discovered columns](https://help.qlik.com/en-US/stitch/integrations/databases/mysql/v2#extraction--discovery)

* [Select records for replication](https://help.qlik.com/en-US/stitch/integrations/databases/mysql/v2#extraction--data-replication)

#### Discovery

During Discovery, Stitch will:

* [Determine table schemas](https://help.qlik.com/en-US/stitch/integrations/databases/mysql/v2#discovery--objects)

* [Type the data in discovered columns](https://help.qlik.com/en-US/stitch/integrations/databases/mysql/v2#discovery--data-types)

##### Determining table schemas

During this phase of Discovery, Stitch queries system tables to retrieve metadata about the objects the Stitch database user has access to. This metadata is used to determine which databases, tables, and columns to display in Stitch for replication.

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

* `SHOW DATABASES`
* `SHOW TABLES FROM [database_name]`
* `SHOW KEYS FROM [table_name]`
* `SELECT * FROM INFORMATION_SCHEMA.TABLES`

##### Data typing

Refer to the [MySQL data types documentation](https://help.qlik.com/en-US/stitch/integrations/databases/mysql#data-types) for more info about how MySQL data is typed for selected columns.

#### Data replication

During data replication, Stitch will:

* [Transform column names to adhere to Avro rules](https://help.qlik.com/en-US/stitch/integrations/databases/mysql/v2#data-replication--column-name-transformations)

##### Column name transformations

To ensure column names are compatible with Avro, the integration will transform column names to adhere to Avro’s rules. In Avro, [column names must](https://avro.apache.org/docs/current/spec.html#names):

* Start with one of the following:
  * `A-Z`
  * `a-z`
  * `_` (underscore)
* Contain only the following:
  * Any characters in the list above (`A-Z`, `_`, etc)
  * `0-9`

If a column name contains an unsupported character, the integration will replace it with an underscore (`_`).