MySQL connector
Set up the MySQL connector in Kaivo: authentication, configuration, the BigQuery tables it syncs, and answers to common questions.
MySQL connector pricing, tier and credits on kaivo.ioKaivo is a fully managed data platform that syncs your MySQL data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your data from MySQL instead of moving it.
What is the MySQL connector
Section titled “What is the MySQL connector”Sync your MySQL tables into BigQuery with Kaivo to report on your application data alongside the rest of your business.
| Category | Files & Databases, Tech |
|---|---|
| Authentication | Username and password |
| Setup | Self-service |
Getting started with the MySQL connector
Section titled “Getting started with the MySQL connector”- Sign up for Kaivo and create a workspace.
- Connect your MySQL account.
- Choose which tables to sync.
- Wait for the initial sync to finish.
- Query your data in BigQuery or your favourite AI or BI tool.
Authenticating MySQL
Section titled “Authenticating MySQL”Connect with your MySQL login. You provide:
| Field | Description |
|---|---|
| Username | |
| Username to access the database. |
| | Password |
Password associated with the username.
|
Configuring the MySQL connector
Section titled “Configuring the MySQL connector”When you set up the connector, you provide:
| Field | Description |
|---|---|
| Host | |
| Hostname of the database, for example “db.example.com”, “mydb-instance.123456789012.us-east-1.rds.amazonaws.com” or “172.217.22.14”. Only public IP addresses are allowed. |
| | Port |
Port of the database.
| | Database |
Name of the database.
|
Tables and columns synced from MySQL
Section titled “Tables and columns synced from MySQL”The available streams and columns mirror the tables and fields in your own database, so they are determined when the connection runs rather than listed here.
How the MySQL sync works
Section titled “How the MySQL sync works”After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where MySQL supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won’t get duplicate rows.
Frequently asked questions
Section titled “Frequently asked questions”How long does the initial sync take for MySQL?
Section titled “How long does the initial sync take for MySQL?”It depends on how much history is in your MySQL account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they’re much faster.
Can I sync only some tables or columns?
Section titled “Can I sync only some tables or columns?”Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don’t select are never copied to your warehouse.
What happens when MySQL’s schema changes?
Section titled “What happens when MySQL’s schema changes?”New fields are never added automatically. You choose which fields to sync, so data you haven’t selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table’s sync mode: full-refresh tables always match what’s currently in MySQL, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.
How do I handle GDPR or data deletion requests?
Section titled “How do I handle GDPR or data deletion requests?”Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in MySQL instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the MySQL connector in Kaivo and all of its synced data is deleted with it.
Common use cases for MySQL data
Section titled “Common use cases for MySQL data”Operational reporting
Section titled “Operational reporting”Bring the tables behind your application into BigQuery for reporting without straining your MySQL database.
Combine with SaaS data
Section titled “Combine with SaaS data”Join your database with CRM, billing, or marketing data in BigQuery for a full picture.
Historical analysis
Section titled “Historical analysis”Keep a synced history of your tables to analyse how records change over time.
One warehouse
Section titled “One warehouse”Centralise MySQL data with the rest of your sources for company-wide reporting.
Use MySQL data in your AI and BI tools
Section titled “Use MySQL data in your AI and BI tools”Once MySQL data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here’s how the most common destinations work with MySQL data.
Claude
Section titled “Claude”Use Kaivo’s MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →
Power BI
Section titled “Power BI”Microsoft’s BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →
Data Studio
Section titled “Data Studio”Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →
Tableau
Section titled “Tableau”The premium analytics standard, with native BigQuery integration. Setup guide →
Google Sheets
Section titled “Google Sheets”Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →
Connect via Power Query’s BigQuery connector. Setup guide →
Metabase
Section titled “Metabase”Open-source BI tool with strong BigQuery support. Setup guide →
See our pricing page for MySQL connector pricing and plan details.