What is our primary use case?
My main use case for MySQL on Ubuntu is storing structured operational database tables, validating the data before it reaches the reports, and running SQL queries. These queries feed directly into my Power BI dashboards. For example, whenever I get a raw source file from my central team or stakeholders, or operational logs for workforce tracking, I load the data into MySQL on Ubuntu and query it using SELECT, JOIN, and aggregations to catch missing values and duplicates. I then pull the clean, properly trimmed datasets into Power BI. That way, I can easily manage data mismatches in SQL instead of troubleshooting broken visuals later on the dashboard.
I handle data mismatches mostly directly inside MySQL on Ubuntu, using SQL validation queries before connecting to Power BI. I run quick GROUP BY queries with HAVING COUNT greater than one to catch duplicates. I also use DISTINCT functions, project record checks, null value checks, CASE statements, and COALESCE to compare counts against the source extracts. Once the logic is completed and verified, I save the files as CSV, because I believe TXT files cannot be fetched properly.
I also work with CSV and XML, and I save the data as an Excel sheet so that I can pull it into Power BI. This keeps the data consistent across the database and each step, without duplicating heavy cleanup steps.
Beyond my main use case, MySQL on Ubuntu helps my workflow by running lightweight jobs and shell scripts right on Ubuntu to schedule routine data checks and automated backups before morning report refreshes. This makes ETL processes easier and report generation simpler.
Running MySQL on Ubuntu also gives me a setup very close to cloud Linux environments such as AWS EC2 or RDS. I test queries, index tables, and check execution times locally before publishing the main data into Power BI, so the process feels faster and we can predict what steps need to be taken.
How has it helped my organization?
MySQL on Ubuntu has had its biggest positive impact through faster data validation, reliable timing, and zero licensing cost for reporting and staging databases. Before using MySQL on Ubuntu as a staging and validation layer to check raw operational extracts for duplicates and missing records before refreshing the Power BI dashboards, the work took hours of manual effort. We used spreadsheets, only Excel and Power Query, running the queries over Power BI and visualizing the data. MySQL on Ubuntu has helped the team a lot, and it has reduced the time we spent as manual effort by 50 to 60%. That time has been saved, and the numbers are very accurate as well.
Beyond the product itself, running the queries and understanding the business logic means the numbers match the requirements coming from the stakeholders. Positively, it is a really good product that has impacted our organization. HR and PMOs are able to focus on the dashboards without asking many questions about what they need to understand. They can consistently get the data and visualize it based on their metrics.
The 50 to 60% time savings from MySQL on Ubuntu has completely shifted how we spend our days. We used to spend a whole day on morning cleanups using VLOOKUP, XLOOKUP, and all the other Excel functions we had built up. We also focused on new KPI fields, Excel charts to visualize the data, and daily updates that required connecting the source data again and reapplying the formulas. The manual formulas were somewhat automated, but not at the level of automation that this product provides.
Since we started working with MySQL on Ubuntu and connecting Excel and Power BI, all of our working procedures have completely changed. As I said, we have saved 50 to 60% of our time. Our manual effort used to revolve around formulas and understanding the logic again and again, and we connected each of these data sources every day, weekly, and thrice a week. MySQL on Ubuntu has reduced much of that. We now fetch the data, understand the logic, and implement the formulas or functions we already know to complete the requirement.
Once that is done, we can collect the data and work directly in Power BI. We do not need to spend more time in Excel running formulas and then fetching the data again to create pivot tables or other outputs. That is how the team has been able to collaborate with each other and deliver the dashboards quickly.
What is most valuable?
From my experience, the best features of MySQL on Ubuntu are its stability, low resource overhead, and strong SQL capabilities. SQL features such as CTEs, window functions, indexing, and views make it super easy to validate large datasets. We can remove duplicates and clean the prep tables before connecting them to Power BI. Pairing MySQL with Ubuntu gives us fast CLI access, easy backups with mysqldump, and full control over the configurations without a heavy OS overhead.
The feature I find most valuable in MySQL on Ubuntu is combining SQL views with proper indexing. When I work with large workforce and operational database tables, joining the raw tables over and over during validation or Power BI refreshes gets really slow. I put indexes on the columns I filter and join on most often, such as employee ID, project codes, and dates, and these queries then run almost instantly, in a snap. I then wrap the validated joins and filters into a clean SQL view, which means Power BI just needs to pull the data from that view to run the dashboard logic. This makes it much simpler to visualize the data and work on the dashboard itself, and it saves a lot of time.
One MySQL on Ubuntu feature I wish more people knew about is EXPLAIN ANALYZE, used along with MySQL Shell and mysqlsh, since most people just run the basic EXPLAIN when a query feels slow. My perspective is that EXPLAIN ANALYZE actually executes the query and shows the real execution times and the rows counted at each step, which exposes missing indexes and bad joins. This is very helpful before the joins are finalized. Ubuntu also gives you Python scripting and fast parallel table imports right from the terminal, which is a huge time saver when loading large CSV files for validation. In my experience, I have not used Python much, but I understand that it is very useful for generating scripts on Ubuntu.
What needs improvement?
From my perspective, MySQL on Ubuntu could be smoother out of the box, even though everything works very well and there is not much to point out. When we start running heavy joins or aggregations for reporting, we have to manually tune the memory settings instead of being guided by a setup wizard. Built-in visual monitoring and query diagnostics are also basic, so I pair MySQL on Ubuntu with external tools such as Grafana or MySQL Workbench on Ubuntu. It feels a little clunky compared to newer SQL clients. Finally, new versions, major upgrades, and authentication plugin changes occasionally break older connectors or BI drivers if we do not test them carefully first. These are the pain points I believe exist with this product.
On the documentation side, the official MySQL manual for MySQL on Ubuntu is super, but it can feel scattered when I am trying to quickly troubleshoot something specific on Ubuntu, such as auth_socket login issues, AppArmor, default MySQL configuration file paths, or other extensions in those paths. More practically, I would like Ubuntu-focused quick start guides for performance tuning and BI connector setup. Some of the SQL and server error codes are still pretty cryptic. I also believe that better alignment between Ubuntu packaging updates and upstream MySQL releases would make day-to-day maintenance much easier.
For cloud deployments of MySQL on Ubuntu, I would suggest three improvements. The first is auto-tuning based on instance memory. Right now, we still have to manually edit the InnoDB settings in MySQL whenever we resize the EC2 instances. The second is simpler storage and AppArmor setup. Moving the data directory to separate EBS volumes and making AppArmor tweaks should be easy to handle through a CLI setup. The third is out-of-the-box cloud backup and monitoring hooks. Lightweight, native options to push backups straight to S3 and export metrics to CloudWatch Logs without writing custom bash scripts would help us.
For how long have I used the solution?
I have been using MySQL on Ubuntu for around three to four years, pretty much alongside my work in workforce analytics and reporting. Whenever I need a lightweight and reliable setup to prepare dashboards in Power BI, I use it as a reliable database to store the structured data and run the validation checks. I can fetch the data using the schemas to check the tables, and once the query is completed, I can easily save the file as an Excel sheet and fetch it into the Power BI dashboard. It has been my go-to setup.
What do I think about the stability of the solution?
In my experience, running MySQL on Ubuntu is very stable, especially on Ubuntu LTS releases using the InnoDB storage engine. This applies across my local Ubuntu validation setup and AWS EC2 instances. Once the starting configuration and memory settings are tuned, the service can run data validation checks directly, and the Power BI dashboard can refresh without any unnecessary data corrections. The only hiccup usually happens around OS or package upgrades if we do not test the connector before we start working on MySQL on Ubuntu. I believe authentication and compatibility are the main priorities to check to ensure the work is efficient.
What do I think about the scalability of the solution?
MySQL on Ubuntu has been very solid for our reporting and validation workloads. Vertical scaling is straightforward when our datasets and Power BI refresh concurrency grow larger and faster. We can resize the VM or AWS instance accordingly without changing any applications or SQL logic. Horizontally, replicas work very well if you need to separate heavy reporting queries from operational writes. If you ever need automatic or multi-node elastic scaling, managed cloud services such as Amazon Aurora and RDS make that easier to maintain.
How are customer service and support?
Since we use MySQL Community Edition on Ubuntu rather than paid Oracle Enterprise support, customer support for MySQL on Ubuntu comes from the community. There is no direct vendor ticket line, so support basically comes down to the community. The community ecosystem is massive, including the official MySQL manual, Stack Overflow, Ask Ubuntu, and DBA forums, and I have never needed to open a formal support ticket. Whenever I hit a snag, such as when tuning the InnoDB memory settings or troubleshooting on Ubuntu, someone has already documented the exact fix online. We can reference it directly from there and start working on our side.
Which solution did I use previously and why did I switch?
Before moving our reporting staging layer to MySQL on Ubuntu, we relied mostly on Excel, with some teams using spreadsheets and local Windows setups to clean and merge the extracts, handle the transformations, and perform data modeling. Once our HR and PMO datasets grew larger, working with multiple spreadsheets and Excel sheets became a huge headache for us in getting the proper data and validating it consistently. Switching to MySQL on Ubuntu gave us a lightweight, zero-licensing-cost relational database where we can properly enforce tables, create schemas, and run repeatable SQL validation checks. We can also easily set it up on AWS instances whenever we need to share the data across the dashboards with our team.
What was our ROI?
We have definitely seen a strong return on investment from MySQL on Ubuntu, mainly through time saved and zero software licensing cost rather than through cutting headcount. Because MySQL on Ubuntu is open source, we have not had to pay per-user or per-server database licensing fees. Ubuntu instances, both locally for validation and on AWS EC2, keep our infrastructure overhead low. On the time side, automating the data validation and pre-building SQL views before refreshing the Power BI dashboards saves 50 to 60% of our manual report time, which is roughly two to three hours saved per reporting cycle. Instead of reducing the team size, the saved time lets our small reporting group handle more HR, PMO, and workforce reports even faster and with fewer manual errors.
What's my experience with pricing, setup cost, and licensing?
We launch a standard Ubuntu instance directly on AWS and install MySQL Server through Ubuntu’s official APT repositories. Since MySQL Community Edition is open source, this keeps licensing cost at zero, avoids third-party AMI markups, and ensures that the AWS cloud instances match our local Ubuntu validation setup with the exact same package versions.
Pricing and licensing were among the biggest reasons we chose MySQL on Ubuntu. Since MySQL Community Edition is open source under the GPL and Ubuntu LTS has no OS licensing fees, our software licensing cost is completely zero. Locally, the setup cost nothing beyond the existing VM resources. On AWS, we just pay the standard EC2 compute and EBS storage rates, which are in the range of tens of dollars a month, depending on the pricing rates given by AWS. Installation takes only a few minutes with MySQL and mysql_secure_installation. The only cost is internal engineering time for initial memory tuning, backups, and security. That is the standard procedure we follow on our organization’s side, and we do not pay for commercial Standard or Enterprise subscriptions.
Which other solutions did I evaluate?
Before setting up MySQL on Ubuntu, we looked at a couple of other options, mainly PostgreSQL and Microsoft SQL Server. We did a huge review of PostgreSQL, which is great and open source. However, for straightforward staging and validation queries that feed the Power BI dashboards, I felt MySQL on Ubuntu was much simpler to get running and keep tuned on Ubuntu without extra complexity. Microsoft SQL Server works really well with Microsoft tooling and Power BI, but the commercial licensing cost does not make sense when we already have a lightweight, zero‐cost, open source stack on Ubuntu that mirrors cleanly onto AWS EC2 instances.
What other advice do I have?
Overall, I give MySQL on Ubuntu an eight out of 10.
I gave MySQL on Ubuntu an eight because, for day-to-day reporting, data validation, and fetching data through Power BI dashboards, it is a rock-solid, fast, and cost-effective setup without any unnecessary headaches. The only reasons it is not a nine or a 10 are the manual setup and tuning work up front, dealing with Ubuntu-specific authentication, and relying on external tools when we want better visual monitoring and smoother client tooling.
Standard open source MySQL does not have native AI capabilities or AI governance. In my workflow, when we connect AI tools or Python scripts to query the data stored in MySQL on Ubuntu, the governance and security are pretty much in our own hands. On the security side, Ubuntu and MySQL give you strong basics such as access control, TLS encryption, SSH tunneling, and auth_socket authentication. You can restrict the AI service account to read-only views. I believe that is a very good point that emphasizes the governance and security of MySQL on Ubuntu with AI capabilities.
MySQL on Ubuntu is a relational database rather than a built-in generative AI tool. I look at accuracy and reliability in terms of how dependably it fits with external AI scripts, Python models, or text-to-SQL tools. From that side, it is super reliable and really amazing. Thanks to InnoDB's ACID compliance, strict schemas, and foreign keys, the underlying data stays connected, consistent, and repeatable, so query results never come back corrupted or unexpected.
Whenever we connect an AI assistant or Python script to generate queries, it gives us summaries or trends, as well as column names and guidance on how to clean the tables and SQL views. These outputs are very accurate, but we still have to double-check complex AI-generated SQL joins before trusting the numbers. It is up to us as users to work on the functions, implement the logic, and run the query. We still check the numbers properly before visualizing them and sharing them with higher management.
In our organization, MySQL on Ubuntu is mostly deployed in a hybrid setup, with a local Linux environment for day-to-day data validation, extracting data, testing queries, and refreshing Power BI dashboards. I run MySQL on Ubuntu in a local Linux environment, and for sharing large workloads, we deploy it on public cloud instances such as AWS EC2 inside a private VPC. The cloud setup behaves exactly the same way as our local setup, which makes the data easy to manage, and it can easily scale up whenever we require.
For public cloud deployments of MySQL on Ubuntu, I primarily use AWS. We run MySQL on Ubuntu EC2 instances inside a private VPC and validate the reporting data there. I am also AWS certified in cloud and on the data engineering side, so it is a natural fit for me for a broader data pipeline and Power BI setup.
My recommendation to others reading reviews is to stick to Ubuntu LTS releases so that you get predictable packaging updates. Do not skip the basics right after installation. Create dedicated read-only users for BI tools instead of using root, and lock down remote access with private VPCs and firewalls. Before loading large datasets or connecting Power BI, adjust the InnoDB settings in my.cnf to match your available RAM and turn on the slow query log. In the end, you get clean SQL views on top of staging tables, so your downstream dashboards will always stay fast and consistent, and they will be easy to troubleshoot.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)