What I like most about MySQL is its reliability and how well it integrates with Java-based backend applications. In my professional development work, I have used MySQL with Spring Boot and Hibernate/JPA for storing and managing application data. I regularly work with relational tables, joins, indexes, CRUD operations, SQL queries, and transaction handling while developing and troubleshooting backend APIs.

The integration with Hibernate/JPA makes database operations easier to manage from the application layer, while MySQL provides predictable query performance and strong transactional consistency. Indexing and proper query design have also been useful when working with larger datasets and improving API response times.

Overall, MySQL fits well into our backend development workflow because it is straightforward to configure, easy to troubleshoot, and integrates smoothly with the Java/Spring ecosystem. Review collected by and hosted on G2.com.

One area that can require additional effort with MySQL is query optimization when working with larger datasets or queries involving multiple tables. In my development work with Spring Boot and Hibernate/JPA, I have occasionally needed to review generated SQL queries, check joins and indexes, and fine-tune queries when database operations affected API response time.

Another area is troubleshooting database-related issues across the application and database layers. When a query or transaction does not behave as expected, identifying whether the issue is in the application logic, Hibernate/JPA mapping, SQL query, or database configuration can take some investigation.

Overall, these are manageable with proper indexing, query optimization, monitoring, and database design, but having better built-in guidance or tooling for identifying inefficient queries and explaining performance bottlenecks could make the development experience easier. Review collected by and hosted on G2.com.

What I like best about MySQL is its simplicity and ease of use. I have been working as a Java developer for around 4 years, and MySQL has been one of the databases I frequently use with Spring Boot applications.

I particularly like MySQL Workbench because of its clean and user-friendly UI. It makes database management, query execution, schema design, and data visualization straightforward. For common CRUD operations, Workbench also provides convenient GUI options, so I don't always have to write every query manually. This saves development time and makes database management easier, especially during development and debugging. Review collected by and hosted on G2.com.

One thing I dislike about MySQL is that some advanced database operations and complex queries can become difficult to manage as the application grows. Query optimization can also require a good understanding of indexing, execution plans, and database design. Additionally, MySQL Workbench can sometimes feel slow when working with large databases or complex schemas. Overall, these are manageable issues, but they can add some extra effort during development and troubleshooting. Review collected by and hosted on G2.com.

What I like most about MySQL is how simple and reliable it is. It’s easy to pick up, performs well for most applications, and benefits from a large community along with excellent documentation. I also appreciate how smoothly it integrates with popular backend frameworks and programming languages, which makes it a solid choice for everything from small personal projects to full production applications. Review collected by and hosted on G2.com.

One thing I dislike about MySQL is that some advanced features such as window functions, common table expressions, and JSON support arrived later than they did in some other relational databases. When applications get larger or more complex, scaling and performance tuning can also take extra effort. And although the documentation is comprehensive, troubleshooting and debugging complex query performance issues isn’t always straightforward, especially for newer developers. Review collected by and hosted on G2.com.

MySQL has been a dependable, well-documented relational database that fits naturally into our backend stack alongside our other integrations like Zoho Books and our internal accounting logic. Performance for our transactional workloads, like trip settlements and journal entries, has been solid and predictable even as data volume grows. The command-line interface and tooling around it are straightforward for our team to work with directly, and being open-source with a strong free community edition makes it a strong ROI choice since we're not paying for enterprise features we don't need. Community support and documentation are extensive, so troubleshooting rarely requires waiting on official support channels. Review collected by and hosted on G2.com.

Some advanced features, like certain types of replication or partitioning, require more manual configuration compared to other database systems, which adds setup overhead for niche use cases. Handling complex queries involving multiple joins across large tables can get slower without careful indexing and optimization work upfront. There's also no built-in AI or intelligent query optimization beyond the standard query planner, so performance tuning still depends heavily on manual expertise rather than automated assistance. Enterprise-tier support and advanced tooling come at additional cost if you outgrow the community edition. Review collected by and hosted on G2.com.

I have starting learning SQL for Language Localization domain and found it really easy to use. Writing & understanding the code is easy. The simple visual keep you intact with the screen. If any errors are there, it explains you where you have to make corrections. Review collected by and hosted on G2.com.

As I am new to the software, nothing I have found something to dislike. As a learner my experience is good and I have started recommending others as well. Review collected by and hosted on G2.com.

I like that it’s a modern MySQL with InnoDB, which is fully ACID compliant by default. This ensures multi-step operations either complete fully or roll back. It also handles large volumes of data and growing user loads without performance degradation. It’s cross-platform and works seamlessly on Linux, Windows, and macOS, which makes it flexible for diverse infrastructure. Review collected by and hosted on G2.com.

Less out-of-the-box functionality overall, and some features require third-party extensions. When migrating to other DBMS platforms, it can also take some tweaking to get everything working smoothly. Historically, it has been less reliable than its peers when it comes to handling transactions, references, and auditing. Review collected by and hosted on G2.com.

ease of use and processes data fast for web apps and large datasets. MySQL delivers massive value because the open-source Community Edition costs $0 in licensing fees, making it one of the most cost-effective database systems available for web applications. Review collected by and hosted on G2.com.

In my experience, MySQL has some limitations when it comes to complex analytical processing, scaling write-heavy workloads, and meeting strict data compliance standards. Review collected by and hosted on G2.com.

What I like best about MySQL is how reliable and efficient it is for ETL-focused analytics work. As a data analyst, I primarily use it to import raw data from CSV files or operational sources, clean inconsistent records, transform datasets, and prepare structured tables for reporting. It gives me a stable environment where I can handle data at scale much faster than working only in spreadsheets.

One of the most valuable aspects for me is the power of SQL for transformations. Using joins, CASE statements, aggregations, window functions, and views allows me to turn messy source data into analysis-ready datasets in a repeatable way. For example, instead of manually combining multiple Excel sheets every week, I can build one reusable query or view and refresh outputs in minutes. That has saved a significant amount of time in recurring reporting workflows.

I also appreciate the performance. Even with larger datasets, queries run efficiently when tables are indexed properly, which is important when working under deadlines. The ability to create stored procedures and scheduled jobs is another advantage because it helps automate repetitive ETL steps.

From a UI perspective, tools like MySQL Workbench make schema browsing, query writing, and table management much easier. It is straightforward enough for daily use while still offering advanced capabilities when needed.

Another major benefit is integration. MySQL connects smoothly with Python, Excel, Power BI, and other BI tools, so it fits naturally into a modern analytics stack. I often use MySQL as the central staging layer before pushing clean data into dashboards.

An unexpected benefit has been how much it improved my thinking as an analyst. Working with relational databases regularly made me better at structuring data models, optimizing logic, and writing scalable processes. Overall, MySQL gives strong ROI because it is dependable, cost-effective, and powerful enough for serious ETL and reporting work. Review collected by and hosted on G2.com.

What I dislike about MySQL is not the core database engine itself, but some limitations around advanced analytics workflows and usability compared with newer cloud-native platforms. As someone who uses it mainly for ETL and data preparation, MySQL handles core SQL tasks very well, but when workflows become more complex, there are areas where it feels less flexible.

One challenge is that performance tuning can require manual effort. For larger joins or transformation-heavy queries, you need to pay close attention to indexing, query design, and execution plans. If tables are not optimized properly, performance can slow down quickly. This means analysts need some database administration knowledge in addition to SQL skills.

Another drawback is that MySQL Workbench, while useful, can occasionally feel slower or less polished when handling very large schemas or multiple open query tabs. For day-to-day querying it works well, but the user experience is not always as smooth as some modern SQL IDEs.

I also feel that native support for advanced analytics and AI-driven capabilities is limited compared with newer data platforms. MySQL is excellent for storing, transforming, and querying structured data, but for predictive analytics, automated insights, or large-scale data science workflows, I usually need to integrate it with Python or external BI tools rather than rely on built-in intelligence features.

Version compatibility and migration between environments can sometimes require extra care as well, especially when moving databases across systems or coordinating with multiple teams using different setups.

That said, none of these issues are deal-breakers for me because MySQL still delivers strong value for ETL and reporting. I simply see it as a powerful traditional database that works best when paired with modern analytics tools rather than as an all-in-one data platform. Review collected by and hosted on G2.com.

MySQL is fairly easy to setup and also to administer. Within 30-45 minutes of install one can have a read heavy reporting web application fully functional and operational. Some other minor refinements are also notable basic views and built in stored procedures are helpful for isolating application vs db logic. Swappable storage engines is also a benefit. Review collected by and hosted on G2.com.

Nothing beats SQLite for simplicity. MySQL is only for Linux not for Windows or Mac really. There is a space for an intermediary database that is not as "complex" as MySQL but more featured than SQLite Review collected by and hosted on G2.com.

MySQL provides an enterprise grade database solution essentially for free. The solution is amazingly powerful, scalable and functional. If you are used to any paid enterprise SQL solution you will feel entirely comfortable using MySQL. SQL is essentially a CLI language, and you will find MySQL is totally fully featured and easy to use. Review collected by and hosted on G2.com.

Some features such as efficient/quick backups and replications are limited to enterprise (paid) versions of MySQL. Some desirable features are unfortunately behind a paywall of sorts, however 99% of useful features are freely available! Review collected by and hosted on G2.com.