MySQL to Databricks integration

Replicate your MySQL data into Databricks with Weld. Automatically replicate the tables you choose from MySQL into Databricks, keeping your analytics layer up to date and ready for querying.

4.8 on G2
MySQLSource
WeldWeld
DatabricksWarehouse
Weld · New sync
MySQLSourceMySQLConnected
Tables to sync

Your own tables, picked when you set up the sync.

  • Extract
  • Load
  • Keep in sync
DatabricksDestinationDatabricksReady
mysql schema
  • mysql.Synced
  • mysql.Syncing
  • mysql.Synced
  • mysql.Synced

Trusted by data and AI teams

  • Flatpay
  • Holafly
  • eComplete
  • Dishoom
  • Danish Endurance
  • Female Invest
  • Son of a Tailor
  • Onomondo
  • Medik8
  • Pas Normal Studios
How it works

How to set up MySQL to Databricks in Weld.
In the app, with the API or an agent.

Weld · New MySQL sync
MySQLNew connectionMySQLAuthorised
Connection namemysql
AuthorizeOpens MySQL to grant read access
Use cases

Why replicate MySQL to Databricks?
Ready for analysis.

Centralizing your MySQL data in Databricks lets you join it with other data sources for cross-platform analytics and deeper insights.

Build reliable dashboards and reports by querying MySQL data directly in Databricks using SQL or your preferred BI tool.

Consolidate data from MySQL alongside other databases and applications in a single cloud data warehouse for a unified analytical layer.

  • Database replication for analytics

    Replicate your MySQL production data to Databricks without impacting database performance. Query historical data without load on your primary database.

  • Centralized data warehouse

    Bring MySQL data into Databricks alongside other sources to create a single source of truth for your organization.

  • Automated reporting

    Replace manual exports and spreadsheet-based reporting with automated pipelines from MySQL to Databricks. Connect BI tools like Looker, Metabase, or Power BI.

Data

What data can you replicate?
From MySQL to Databricks.

Weld syncs the objects the MySQL connector exposes into Databricks, and you choose which tables and fields to include. The connector's docs list what is available.

    Weld MCP server

    Ask your agent.
    It queries Databricks for you.

    Connect Claude, Cursor, ChatGPT or your own agent to Weld over MCP. It reads the MySQL context, finds the tables it needs and runs the query in Databricks.

    Claude CodeOpus 5
    >

    Which MySQL tables do we have in Databricks, and which is the largest?

    Looking up what Weld has synced from MySQL.

    ●weld·search_available_references
    ⎿raw.mysql.*
    tables, columns and freshness
    ●weld·get_reference_schema
    ⎿columns, types and nullability
    ●weld·run_query
    ⎿select count(*) from {{raw.mysql.…}}
    submitted
    ●weld·get_query_status
    ⎿DONE
    ●weld·get_query_result
    ⎿rows returned
    ✓Answered from MySQL data in Databricks
    >Ask about your MySQL data
    Under the hood

    Technical considerations.
    What to expect.

    Incremental syncing
    Weld uses incremental syncing where supported by the MySQL API, loading only new and updated records to minimize data transfer and warehouse costs.
    Change data capture
    For MySQL, Weld can use log-based replication (CDC) to capture inserts, updates, and deletes without querying the entire table on every sync.
    Schema handling
    Weld automatically manages schema changes. If MySQL adds new fields, they're detected and added to the corresponding Databricks tables.
    Data freshness
    Sync frequency depends on your Weld plan. Most connectors support schedules from every 5 minutes up to daily intervals.
    Security
    All data is encrypted in transit (TLS) and at rest. Weld is SOC 2 Type II compliant and supports IP whitelisting for database connections.
    FAQ

    Common questions.
    About MySQL to Databricks.

    Start syncing MySQL to Databricks.

    Set up your MySQL data pipeline in minutes. No credit card required. Free for 14 days.

    MySQLSource
    WeldWeld
    DatabricksWarehouse