What to Check Before Ingesting from MySQL

May 2026

MySQL ingestion is smoother when you decide whether the first run should auto-discover tables or target a small list, then verify the connection from the runner itself.

Short Answer

Before ingesting from MySQL, verify the mysql://user:pass@host:3306/db connection string, confirm the runner can reach that host and port, decide whether to let Skippr auto-discover readable tables or provide an explicit tables list, and clarify whether the long-term plan includes CDC via binlog replication. The connector works for straightforward table reads, but the first ingestion is much easier to reason about when the team agrees on exactly which tables should appear on day one.

For example, a DSN pointing at mysql://etl:secret@db.internal:3306/app may connect cleanly while still surprising the team if tables is omitted and Skippr discovers every readable table in that database. If the goal is only customers and orders, make that explicit before the first run so "success" does not mean an unexpectedly wide extraction.

Why Teams Struggle with This

MySQL first-ingestion problems are often about scope rather than raw connectivity. Engineers may confirm the database is up, then forget to ask whether the first pipeline should discover everything, read a curated subset, or prepare for a later CDC setup with different operational requirements.

• The connection string has to be correct for both authentication and database selection, not just host reachability.
• Omitting tables hands discovery to Skippr, which is useful but should be intentional.
• The MySQL user still needs read access on whatever tables the first ingestion will touch.
• If CDC is the next step, plan for binlog-related requirements early instead of treating them as a surprise after the batch read works.

How Skippr Handles It

Skippr makes the MySQL source easy to stage. You can start with a plain connection string and optionally constrain the first pass to a short list of schema.table names. That gives teams a controlled way to validate extraction before broadening coverage.

The connector docs also point cleanly to CDC when the project needs to evolve from table reads into an ongoing mutation pipeline. That separation helps teams avoid overloading the first ingestion with requirements they have not actually prepared yet.

• MySQL source configuration through a single connection string and optional tables list.
• Auto-discovery for readable tables when broad extraction is intentional.
• A clear path from initial table reads to later binlog-based CDC if the project expands.
• Troubleshooting guidance centered on authentication, host reachability, and missing-table expectations.

What the First Useful Version Looks Like

A strong first MySQL pipeline usually names a small set of business tables instead of using broad discovery immediately.

If the team cannot explain which tables should appear after the first run, tighten that scope before you start ingesting.