ATX AnalyticsTable reports on the operational MySQL databases behind your applications without touching them: a read-only session, the query, a DuckDB copy in the project for analysis, and personal data masked before an extract leaves your machine. It speaks to MySQL, MariaDB, Aurora MySQL, TiDB and SingleStore.
The MySQL connection form in ATX AnalyticsTable 1.7, filled in with the example values below. Secrets go into the encrypted vault, never into the project.
Map the managed identity (as the Entra admin of Azure Database for MySQL): CREATE AADUSER 'atx-reporting' IDENTIFIED BY '<client ID of the managed identity>'; GRANT SELECT ON orders.* TO 'atx-reporting'@'%';
Reporting query — e-mails hashed in MySQL: SELECT DATE(o.created_at) AS day, o.country, SHA2(LOWER(o.customer_email), 256) AS customer_key, COUNT(*) AS orders, SUM(o.total_gross) AS revenue FROM orders o WHERE o.created_at >= CURDATE() - INTERVAL 30 DAY GROUP BY day, o.country, customer_key ORDER BY day;
Then reshape locally — a Run SQL step on the project's DuckDB: -- "input" is the table the previous pipeline step produced (the import above). -- This runs on your machine, in the project's DuckDB, not on the database. SELECT region, SUM(revenue) AS revenue, COUNT(DISTINCT customer_key) AS customers FROM input GROUP BY region ORDER BY revenue DESC; — Column names follow the query above; on the local engine the pipeline's current table is registered as input before the script runs.
MySQL has no row-level security, so restricted views and grants are the native tools, and they apply to the database user. Running queries as the signed-in person works only on Azure Database for MySQL with an Entra mode; everywhere else the connection's user is shared and per-person masking belongs in the project's data-access policy.
A refresh needs a route to port 3306. The imported copy and all reports over it work offline on your machine; the licence validates offline.
Entra, Cloud SQL IAM, RDS IAM and LDAP send their credential through the clear-text plugin, so they require TLS: DISABLED and PREFERRED are refused for them and a blank mode becomes REQUIRED.
Yes — choose the engine variant so server settings are spelled correctly. TiDB and SingleStore are supported the same way.
Yes. Enter a comma-separated host list; it is tried in order, for example both MySQL Router endpoints of an InnoDB Cluster.
This site needs JavaScript for the full experience. Every page above is reachable without it.