Last updated on Jul 26, 2023

Hevo can load data from any of your Pipelines into a MySQL database. In this document, we will walk through the steps to add MySQL as a Destination.

We do not recommend using MySQL as a Destination for building your production Pipelines. It can perform poorly even for low volumes of data. If you run into performance issues, these may be unresolvable, and you will have to migrate to a different Destination. Read Limitations of using MySQL as a Destination.

Destination Considerations

  • You must disable any foreign keys defined in the target tables. Foreign keys do not allow data to be loaded until the reference table has a corresponding key defined.
  • You can replicate data for only 4090 columns in a given MySQL table. Read Limits on the Number of Columns.

Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Apr-25-2023 2.12 Updated section, Configure MySQL Connection Settings to add information that you must specify all fields to create a Pipeline.
Jan-10-2023 NA - Removed section, Limitations and relocated its content to the Limitations of using MySQL as a Destination page.
Dec-07-2022 NA Updated section, Limitations to provide information about MySQL as a Destination.
Sep-07-2022 NA Added the following sections:
- Prerequisites,
- Whitelist Hevo’s IP Addresses,
- Grant Permissions to the Database User.
- Updated the Configure MySQL Connection Settings to add a link to the Connecting to a Local Database page.
- Deleted the Connect to a Local Database section.
Feb-21-2022 1.82 Updated section, Configure MySQL Connection Settings to provide support for SSL in MySQL as a Destination.
Jul-26-2021 1.68 Added section, Connect to a Local Database.
Jul-12-2021 NA Updated the section, Destination Considerations.

Tell us what went wrong