Skip to main content

Import from MySQL

Use a MySQL import job to load existing MySQL data into VeloDB Cloud and keep the target tables updated through CDC.

Prerequisites​

  • MySQL import is supported only for VeloDB Cloud warehouses running the 26.x series.
  • The MySQL source must be compatible with MySQL 5.6, 5.7, or 8.0.x.
  • A VeloDB Cloud warehouse that can reach the MySQL host and port.
  • A MySQL user with the permissions required to read the selected databases and tables.
  • Binary logging enabled on the MySQL source.
  • A target database in VeloDB Cloud, or permission to create one during the wizard.

For AWS-managed MySQL sources, complete the source-side prerequisites before creating the import job:

Create the import job​

  1. Open Import from the ingestion group, then click + Add Import Job.
  2. Select MySQL.
  3. Enter the job name, MySQL host, port, database, username, password, and SSL settings if required.
  4. If the MySQL source is in a private VPC, enable Private Link and configure the PrivateLink connection in the wizard. For setup details, see Grant VeloDB access to your VPC.
  5. Select the target database.
  6. Choose the sync type:
    • Initial Load + Incremental Sync: loads existing data first, then captures ongoing changes.
    • Incremental Sync only: captures only new changes from the configured offset.
  7. Select the schemas and tables to ingest. Expand a table to configure column-level filtering if needed.
  8. Configure the sync interval and strict mode.
  9. Run the pre-checks. When all checks succeed, start the job.

View job details​

In the import job list, click a MySQL import job to open its details page.

For a MySQL import job, the details page provides monitoring views such as:

  • Sync Rows
  • Imported Size
  • Sync Task Failure Count

You can also configure monitoring for Sync Task Failure and open the corresponding Task Details to inspect failed sync tasks.

Troubleshooting​

  • If connectivity checks fail, verify the host, port, security group, firewall, and PrivateLink configuration.
  • If CDC checks fail, verify binary logging and replication permissions on the MySQL source.
  • If rows fail to load, review column types, strict-mode behavior, and column filters.