
MySQL data in your warehouse
Yres reads a MySQL database through a direct connection: host, port (3306 by default), the name of the schema or database, and an account with read access. If MySQL is publicly reachable, Yres uses the Azure Data Factory cloud runtime; if the server is on-premises or behind a firewall, you pick a self-hosted integration runtime. Per table you decide which columns are included and whether it loads in full or on changes only. The data arrives with history in an Azure SQL database in your own tenant, ready for Power BI.
If a single web shop or application runs on MySQL and you only want to see the current figures, a direct connection or an export will take you a long way.
Yres earns its place when you want to bring application data from MySQL together with your financial and other sources, when tables grow so large that you only want to fetch the changes, or when you want to see what an order, customer or price looked like earlier.
Yes. Like the other database sources, MySQL supports two change columns. They must share the same data type; per row the higher of the two counts. A new record where only the created column is filled is therefore not skipped.
In MySQL those are the same thing. You enter the name of the schema, in other words the database, you want to load from. SHOW DATABASES; lists the available names, or ask your administrator.
A self-hosted integration runtime that can reach the MySQL server. It has to be installed and published before you create the source; you then select it when adding the source.
Per table you tick the columns you want to load; at least one. Per column you can also set whether a change in that column should produce a new version of the row, and adjust the target type in the data warehouse.
Full technical description in the knowledge base →·Last reviewed:
Built for organisations on Azure and Power BI. Yres connects your sources, keeps the history and promotes changes in a controlled way, without manual work.