Looker Studio talks to MySQL out of the box, so this takes about five minutes. Whether it should talk to that particular MySQL server is the more interesting question.
The connection is trivial: host, port, database, user, password, done. What's easy to miss is that you've just made your production database the backend of a reporting tool. Looker Studio queries when a report opens, when someone changes a filter, and when the cache expires — and it does that for every person holding the link.
There's also a firewall decision buried in the setup. Looker Studio connects from Google's infrastructure, so your database has to accept connections from a broad published range of addresses. That's a materially different security posture from a database only your application can reach, and it's easy to agree to while thinking about charts.
Then the practical annoyance: a dashboard pointed at raw tables gets slower as the tables grow, and MySQL's type quirks surface as chart errors. Zero-dates like '0000-00-00' aren't valid timestamps anywhere outside MySQL, and they turn into broken date dimensions rather than a clear error message.
All three give Looker Studio a database to read. They differ in which database, and in what a slow report can cost you.
The built-in MySQL connector, pointed at your live server with a read-only user.
Stand up a MySQL replica and point Looker Studio at that instead.
BeQuery maintains a verified PostgreSQL copy of the MySQL database, read by Looker Studio's built-in PostgreSQL connector.
Read-only MySQL credentials, host and port. BeQuery clones the database into an isolated PostgreSQL copy, verified against the source on every sync.
In Settings → External connections, generate a PostgreSQL user scoped to your team's schema. It is SELECT-only: it cannot write, alter or drop anything, and it can't see another workspace. External connections are available on the Cloud and Enterprise plans.
Add data → PostgreSQL → paste the host, database, user and password. No community connector, no OAuth dance, nothing to install: PostgreSQL is one of Looker Studio's built-in connectors.
Choose the custom query option and paste SQL that already aggregates. Your report then reads a few hundred rows instead of scanning your largest table on every interaction — which keeps dashboards fast and stays inside the 30-second statement timeout on external credentials.
Both are defensible. The deciding factor is usually how many people hold the link and how much your production database has to lose.
Yes — PostgreSQL is one of the built-in connectors, on equal footing with MySQL. That's what makes the clone route work without any export step: BeQuery's copy is an ordinary PostgreSQL database, so Looker Studio reads it with a stock connector, no community add-on and no subscription.
It can — MySQL is a built-in connector, and for a small shop that's a legitimate choice. What you're accepting is that your production database has to be reachable from Google's IP ranges, and that every viewer opening the report, and every scheduled refresh, runs queries against the server your customers are checking out on. It works fine until the report gets popular or someone builds a dashboard with twelve charts on it.
No, and this is the real difference from the BigQuery route. Looker Studio speaks PostgreSQL natively, and BeQuery's clone is a real PostgreSQL database — so the report reads the copy directly. There's no load step to schedule and nothing to keep in sync beyond the sync you already have.
External PostgreSQL credentials — the thing Looker Studio connects with — are available on the Cloud (pay-as-you-go) and Enterprise plans. The clone itself, the SQL editor and the in-app dashboards work on every plan, including the free tier.
As fresh as your last sync, plus whatever caching you leave on in Looker Studio. Sync runs nightly on lower plans and down to roughly every minute on higher ones. For a report someone opens each morning, nightly is usually what people settle on anyway.
Free tier, no credit card, read-only access. Production is never written to — and you can explore the demo store before connecting anything.