MySQL source

The MySQL source supports both cloud and on-premises databases. To connect to an on-premises database, your environment must have a self-managed Groundplex configured in the Classic Manager shared folder. Refer to Connect to on-premises endpoints for more information.

When you select MySQL, if AutoSync detects that a Groundplex is available, a dialog opens that enables you to select a cloud or on-premises database. For an on-premises database, you must also select a Groundplex.

To use the incremental load type, you'll need to select a column that contains the last updated timestamp for each table. If no such column exists, you can:
  • Create it in the source first.
  • Use Full load instead. Full load drops the target tables and reloads them on synchronization. It does not require a timestamp column that tracks updates. AutoSync uses this load type by default if you do not select a timestamp column.

A timestamp column must be one of the following types:

  • datetime
  • timestamp

Supported account types

Create your MySQL Account in Classic Manager or AutoSync Manager, using the following account type:

  • MySQL Database Account

Known limitations

  • MySQL credentials cannot be created in AutoSync because they need an updated JDBC JAR file. As a work around, create the Account in the IIP and specify the correct JAR file. Learn more about configuring MySQL Accounts.


To configure MySQL as a source:

  • Select existing credentials: From the drop-down list, select credentials created in the IIP.
  • Select schema: From the drop-down list, choose the source schema. AutoSync populates the list from your MySQL account.
  • Select tables to synchronize: From the drop-down list, choose a table to synchronize.
  • Select the column that tracks the last modified time: To use Incremental load, select a timestamp column. This column must not be nullable and can't contain any null values. To use Full load, leave this field empty.
  • Click Select another table to add another table to synchronize.