--- title: MySQL Reviews meta_title: 'MySQL Reviews November 2026: Details, Pricing, & Features | G2' meta_description: Filter 1688 reviews by the user's company size, role or industry to find out how MySQL works for a business like yours (as of November 2026). aggregate_rating: rating_value: 4.4 review_count: 1688 scale: '5' date_modified: '2026-11-20' parent_category: name: Database Software url: https://www.g2.com/categories/database-software ---

MySQL Reviews & Product Details

Profile Status

This profile is currently managed by MySQL but has limited features.

Are you part of the MySQL team? Upgrade your plan to enhance your branding and engage with visitors to your profile!

Pricing

Pricing provided by MySQL.

Basic

$2,000.00
Per User Per Year

User Insights

Average based on 1688 real user reviews.

Implementation Time

2 months

Perceived Cost

$$$$$

Typical contract price

$0k - $0k

Sign in to view

Per Year

MySQL Reviews FAQs

Generated using AI

What is MySQL, and what problem is it built to solve?

MySQL is a relational database management system used to store, organize, and retrieve structured data. It serves as a data layer for applications and supports tasks such as managing application records, transactions, and reporting data.

What company sizes and industries is MySQL the best fit for?

MySQL is used by small businesses, mid-market organizations, and enterprises, with particularly strong representation in software and IT-related work. Its use spans several company sizes and industries:
  • Small businesses: Commonly used for application back ends, web projects, and database learning.
  • Mid-market organizations: Used for business applications, data management, and reporting.
  • Enterprise organizations: Used for application data, transactions, and operational databases.
  • Software and IT services: A recurring setting for development, web applications, and database administration.
  • Other sectors: Use also appears in education, financial services, telecommunications, and logistics.

How long does it take to implement MySQL across a team?

Implementation can be quick for straightforward deployments: under a month is the most commonly reported go-live range. Teams also report launches in under a day, while some implementations take several months.
Time to go live Relative frequency
Under 1 month Most common reported range
Under 1 day Also commonly reported
1–3 months Also reported
3–6 months Reported less often

What customer support options does MySQL provide, and how do users find the overall support experience?

MySQL offers support through chat and phone, including 24/7 live-rep support, along with self-service resources and email/help-desk channels. The support experience is mixed: users value the documentation, forums, and community help, while direct support and ticket response can be less consistent.

What is the experience like for teams switching to MySQL from another tool?

Switching to MySQL has been driven by lower licensing and operating costs, simpler setup, and a preference for a relational database that fits existing development stacks. Users describe moves from other commercial relational databases as well as local or nonrelational systems; transitions can require code rewrites or schema adjustments, but MySQL’s familiar SQL and application integrations help teams get established.

What tools and platforms does MySQL integrate with, and how do these integrations help users get more value from the product?

MySQL offers 24 integrations. In everyday workflows, the named connections help teams use it as a database behind applications, development environments, and reporting tools.
  • Application development: Spring Boot, PHP, and Node.js.
  • Developer tools: Eclipse.
  • Analytics and spreadsheets: Microsoft Power BI and Microsoft Excel.
  • Web infrastructure: Apache HTTP Server Project.
These connections let teams work with application data in their existing development stack and bring database information into reporting and analysis workflows.

What features or capabilities could make MySQL even more useful?

MySQL could be more useful with stronger assistance for diagnosing and tuning queries, along with improvements to its management interface. Recurring improvement areas include:
  • Query troubleshooting: Make error messages, debugging, and performance guidance clearer, especially for complex queries.
  • Administration and usability: Modernize the interface and make routine database management and configuration more straightforward.
  • Advanced workloads: Expand capabilities for analytics, complex data types, and scaling demanding workloads.
  • Operations: Simplify replication, backups, and data import and export for larger databases.

Is MySQL considered safe and secure for handling data?

MySQL is used to handle business and application data, and users describe relying on access controls and permissions to restrict who can view or change it. Security sentiment is not uniform: some users value these protections, while others find that securing and configuring the database takes care, particularly for more demanding environments.

MySQL Reviews (1,688)

View 3 Video Reviews
Reviews

MySQL Reviews (1,688)

View 3 Video Reviews
4.4
1,688 reviews

What do users say?

Generated using AI from real user reviews

Pros & Cons

Generated from real user reviews
View All Pros and Cons
Search reviews
Filter Reviews
Clear Results
G2 reviews are authentic and verified.
Nikhil C.
NC
Nikhil C.
Associate System Engineer
Enterprise (> 1000 emp.)
Originally submitted 9/15/2026
"MySQL: Reliable, High-Performance, and Seamlessly Integrates with Spring Boot & Hibernate"
5/5
What do you like best about MySQL?

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.

What do you dislike about MySQL?

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.

Kartik S.
KS
Kartik S.
Article Trainee
Mid-Market (51-1000 emp.)
"Reliable, Efficient Database Management—With Room to Scale"
4.5/5
What do you like best about MySQL?

I use MySQL to store, manage, and retrieve data efficiently. I like its simplicity, speed, and reliability. It’s easy to use, handles data efficiently, and makes running queries and managing databases convenient. It helps me manage large amounts of data, reduce manual work, retrieve information quickly, and maintain accuracy. Its flexibility lets me manage different types of data, its security features help protect important information, and its compatibility with programming languages makes integration with applications smooth. I also like that it’s open source and has a supportive community. It saves me time and makes database management more organized and efficient. The initial setup was fairly easy and straightforward: installation was simple, and MySQL Workbench made connecting to and managing databases convenient. A little guidance was helpful during setup. I also find MySQL Workbench and Excel useful alongside MySQL for managing, analyzing, and organizing data. I’d rate MySQL 9 out of 10; I find it reliable, efficient, and easy to use. Review collected by and hosted on G2.com.

What do you dislike about MySQL?

I find performance optimization can be challenging with very large and complex databases. I’d also like a more beginner-friendly, intuitive interface, with interactive tutorials and step-by-step guidance. Troubleshooting could be simpler with clearer error messages, and automated optimization tools, better query suggestions, and easier database monitoring would help when handling large datasets. Review collected by and hosted on G2.com.

Aditya A.
AA
Aditya A.
YouTube Content Creator
Mid-Market (51-1000 emp.)
Business partner of the seller or seller's competitor, not included in G2 scores.
"Easy to Use with Workbench, but Slows Down on Large Databases"
3.5/5
What do you like best about MySQL?

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.

What do you dislike about MySQL?

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.

K Vasanth K.
KK
K Vasanth K.
Global Information Technology Intern
Information Technology and Services
Small-Business (50 or fewer emp.)
Originally submitted 8/2/2026
"Simple, Reliable, and Easy to Integrate—RDBMS at Its Best"
5/5
What do you like best about MySQL?

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.

What do you dislike about MySQL?

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.

Muhammed A.
MA
Muhammed A.
Technical Project Manager
Logistics and Supply Chain
Mid-Market (51-1000 emp.)
"Dependable, Well-Documented MySQL with Solid Performance and Strong ROI"
4.5/5
What do you like best about MySQL?

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.

What do you dislike about MySQL?

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.

Anand K.
AK
Anand K.
Copywriter (Client Solution)
Small-Business (50 or fewer emp.)
"Looking for SQL? Go for MySQL"
5/5
What do you like best about MySQL?

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.

What do you dislike about MySQL?

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.

JD
Janani D.
Senior Data Engineer
Enterprise (> 1000 emp.)
"Modern, ACID-Compliant MySQL with Strong Scalability"
3.5/5
What do you like best about MySQL?

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.

What do you dislike about MySQL?

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.

Saubhagya J.
SJ
Saubhagya J.
Software Engineering Specialist
Computer Software
Mid-Market (51-1000 emp.)
"Easy to Use and Fast for Web Apps and Large Datasets"
5/5
What do you like best about MySQL?

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.

What do you dislike about MySQL?

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.

Aparajito P.
AP
Aparajito P.
NA
Small-Business (50 or fewer emp.)
"MySQL: Reliable, Fast ETL and Reporting with Powerful SQL"
5/5
What do you like best about MySQL?

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 do you dislike about MySQL?

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.

Verified User in Consulting
AC
Verified User in Consulting
Small-Business (50 or fewer emp.)
"Easy to Set Up and Administer—MySQL Gets Reporting Apps Running Fast"
4.5/5
What do you like best about MySQL?

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.

What do you dislike about MySQL?

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.

Questions about MySQL? Ask real users or explore answers from the community

Get practical answers, real workflows, and honest pros and cons from the G2 community or share your insights.

GU
Guest User
•
Last activity 5 months ago

Can I use MySQL for free?

2 Upvotes
4
Join the conversation
Shruti N.
SN
Shruti Nair
•
Last activity 7 months ago

Best relational database software for tech startups

Pricing Options

Pricing provided by MySQL.

Basic

$2,000.00
Per User Per Year
MySQL Comparisons
MySQL Features
Data Schema
Query Language
Database Locking
Access Control
Storage
Availability
Stability
Text Search
Data Types
Languages