You have an application database in MySQL. You want to model it — staging tables, tests, incremental facts, the usual dbt shape. So you go looking for dbt-mysql.
You will find one. It was last released in April 2024, and it pins dbt-core 1.7.
That pin is the whole story, and it is worth understanding before you decide anything else.
What a version pin on your transformation layer costs
An adapter that pins an old dbt-core does not just deny you new dbt features. It holds the floor down for everything that shares the environment. dbt-core pulls in a substantial dependency tree, and pinning it to a 2023-era minor version pins large parts of that tree with it. Security updates elsewhere in your stack start colliding with the pin, and the usual resolution is to stop upgrading.
So the cost is not "we are on an older dbt". The cost is that one adapter, for one database you did not especially need to transform in, becomes the constraint on your whole transformation environment.
We looked at shipping it anyway. We decided not to, and we say so on the MySQL connector page rather than leaving people to find out at the first run.
MySQL is a source, and that is not a consolation prize
The instinct when a tool cannot transform in place is to treat it as a gap. It is worth pushing back on that.
Your MySQL instance is serving an application. It is sized for transactional reads and writes, its indexes are tuned for the queries your product makes, and the last thing it needs is a nightly wave of analytical scans building wide aggregate tables next to production traffic. Transforming in your operational database is usually the wrong idea even when the tooling supports it.
The shape that works is the one ELT was named for:
- Extract from MySQL — a whole database, or one table at a time.
- Load into a warehouse, raw and untransformed.
- Transform there, with dbt, where the compute is separate from the database your customers are hitting.
Step 3 is where your dbt project lives, and the adapter question moves to the warehouse — which is a much better place for it, because that is where the maintained adapters are.
Where you can actually run dbt
These are all dbt transformation targets, and all of them are destinations you can land MySQL data into:
PostgreSQL · SQL Server · ClickHouse · DuckDB · BigQuery · Snowflake · Redshift
That list covers most of the reasonable answers. If you already have a warehouse, you almost certainly have one of these. If you do not, DuckDB is a genuinely serious option for small-to-mid volumes and costs nothing to try; Snowflake and BigQuery are the usual answers once concurrency matters.
The pattern is identical whichever you pick, and we walked through it end to end for a different source in PostgreSQL to BigQuery — the extraction side changes, the modelling side does not.
One thing our own tool will not do
Symmetry demands this bit.
MySQL is not a destination in Datanika either. You can extract from it; you cannot load into it. The upload form does not offer MySQL as a destination, and creating an upload that names one anyway — through the API, for example — is refused with a message that says exactly that.
It is worth being precise about why, because the easy version of that sentence is wrong. The load library underneath us, dlt, can write to MySQL, through its generic SQLAlchemy destination. Datanika does not use that path, so the limit is ours rather than dlt's. We mention it for the same reason it is on the connector page: if you were planning MySQL → MySQL replication, you should find that out from a blog post rather than from a refused form.
The short version
- There is no maintained dbt adapter for MySQL, and the unmaintained one pins your transformation environment to 2023.
- That is not the blocker it first appears, because transforming inside your operational database was already the wrong architecture.
- Extract from MySQL, land in a warehouse, run dbt there. The MySQL setup guide covers the extraction half.
- If you specifically need MySQL as a target, Datanika does not support it. dlt's SQLAlchemy destination can, if you are willing to run dlt yourself.
Datanika is an open-source data platform — extraction, loading, transformation and scheduling in one place. Every connector page lists what the connector cannot do, next to what it can.
Top comments (1)
The version pin is the sharp edge here. Beyond dependency collisions, running dbt in operational MySQL hits hard concurrency ceilings. MySQL relies heavily on table and row-level locks during write-heavy analytical transformations like creating staging tables or running incremental updates. In production environments, running those scans alongside real-time transactional reads and writes frequently triggers metadata locks and lock wait timeouts on application threads. Moving transformations downstream into DuckDB or Snowflake completely isolates analytical compute from transactional latency.