Sync data from BigQuery to MySQL

CloudQuery is the simple, fast data integration platform that can replicate your data from BigQuery to MySQL

Trusted by

Self-hosted

Start locally, then deploy to a Virtual Machine, Kubernetes, or anywhere else. Full instructions on CLI setup are available in our documentation.

Step-by-step Instructions

Cloud-hosted

Start syncing in a few clicks. No need to deploy your own infrastructure.

Coming soon for BigQuery to MySQL

Fast and reliable

CloudQuery’s efficient design means our syncs are fast and a sync from BigQuery to MySQL can be completed in a fraction of the time compared to other tools.

Easy to use, easy to maintain

BigQuery syncing using CloudQuery is easy to set up and maintain thanks to its simple YAML configuration. Once synced, you can use normal SQL queries to work with your data.

A huge library of supported destinations

MySQL isn’t the only place we can sync your BigQuery data to. Whatever you need to do with your BigQuery data, CloudQuery can make it happen. We support a huge range of destinations, customizable transformations for ETL, and we regularly release new plugins.

Extensible and Open Source SDK

Write your own connectors in any language by utilizing the CloudQuery open source SDK powered by Apache Arrow. Get out-of-the-box scheduling, rate-limiting, transformation, documentation and much more.

Step by step guide for how to export data from BigQuery to MySQL

MacOS Windows Linux

MacOS Setup

Step 1: Install CloudQuery

To install CloudQuery, run the following command in your terminal:

brew install cloudquery/tap/cloudquery

Step 2: Create a Configuration File

Next, run the following command to initialize a sync configuration file for BigQuery to MySQL:

cloudquery init --source=bigquery --destination=mysql

This will generate a config file named bigquery_to_mysql.yaml. Follow the instructions to fill out the necessary fields to authenticate against your own environment.

Next, log in to the CloudQuery CLI. If you have't already, you can sign up for a free account as part of this step:

cloudquery login

Step 4: Run a Sync

cloudquery sync bigquery_to_mysql.yaml

This will start syncing data from the BigQuery database to your MySQL database! 🚀

See the CloudQuery documentation portal for more deployment guides, options and further tips.

FAQs

What is CloudQuery?

CloudQuery is an open-source tool that helps you extract, transform, and load cloud asset data from various sources into databases for security, compliance, and visibility.

Why does CloudQuery require login?

Logging in allows CloudQuery to authenticate your access to the CloudQuery Hub and monitor usage for billing purposes. Data synced with CloudQuery remains private to your environment and is not shared with our servers or any third parties.

What data does CloudQuery have access to?

CloudQuery accesses only the metadata and configurations of your cloud resources that you specify without touching sensitive data or workloads.

How is CloudQuery priced?

CloudQuery offers flexible pricing based on the number of cloud accounts and usage. Visit our pricing page for detailed plans.

Is there a free version of CloudQuery?

Yes, CloudQuery offers a free plan that includes basic features, perfect for smaller teams or personal use. More details can be found on our pricing page.

What credentials do I need in order to sync data from BigQuery to MySQL?

We use application default credentials in order to sync from BigQuery to MySQL. The best option to use depends on the environment in which your sync is running. Full details can be found here.

What versions of MySQL can CloudQuery sync to from BigQuery?

By default, the CloudQuery MySQL integration supports versions 8.0 and later. If you need to sync to an earlier version of MySQL, please get in touch with the team and we’ll find a way to help.

Does the CloudQuery MySQL integration support MariaDB?

The CloudQuery MySQL integration does not yet fully support MariaDB. If this is important to your use case, then we would encourage you to upvote the odeon GitHub issue so that we can dedicate development resources to introducing full support.