We performed a comparison between MYSQL and SQL Server based on our users’ reviews in four categories. After reading the collected data, you can find our conclusion below.
Comparison Results: SQL Server comes out ahead in this comparison because it is less demanding on resources and can more easily be integrated with other solutions. Some users feel that MySQL requires more maintenance and can be a bit buggy and less stable than SQL Server.
"MySQL is easy to use, has fast performance, and it is comfortable for end-user to use. The schema level and structure we are using are very simple and easy to understand. Additionally, packaging tool development is straightforward and the data is presented in a way that is very simple to understand."
"The solution is free to use, which is its most valuable aspect."
"I like MySQL because of its community."
"What I really like about MySQL is the opportunity to search for information and organize it any way I like."
"MySQL is a light database. It's not very complex. It's easy to develop, easy to maintain, and easy to back up and restore."
"It is very easy to install and has all basic database features."
"It has a lot of features. The RDBMS, consistency, and multi-user features are valuable."
"The initial setup was easy. I work in an agile way, which means coding and deploying quickly."
"SQL Server is widely used and it's simple. You cannot do without Microsoft if you want to manage IT for a business customer."
"I have found that SQL Server works very well in the Microsoft Dynamics environment."
"The most valuable features for database management in SQL Server are SQL Server Management Studio and Visual Studio Code with its administration capabilities."
"I value the ability it gives me to test on small machines and easily scale up to larger devices for live applications."
"I use the menu on the management view credit section to get information from the database."
"The main feature of this solution is ease of use."
"SQL Server's Management Studio is very user friendly. I like their database and the additional features it offers. It's also easy to integrate SQL Server with things like CLR, PowerShell, and command shell"
"The product can scale if a company needs it to."
"I would like to improve the solution’s pricing for licenses."
"They should come up with a better solution than the NDB cluster for better scaling. If they could come up with a better solution for write scaling, apart from the NDB cluster, which is supported by all open source communities, that would be great. Although the NDB cluster, I believe, is an open-source tool, it's not widely supported as a solution."
"The GUI could improve in MySQL."
"There should be an arrangement for end-users to get trained to use the tool...Improvement-wise, a graphical interface could be added for new users, eliminating the need to memorize the complex syntax."
"The solution could have better integration and security features."
"Stability needs improvement and the backup needs to be enhanced."
"Since we upgraded from 8.0.12 to 8.0.22, it has had some slowness-related issues. Some of the queries that were fast previously are quite slow now. I did some research, and I found many people complaining about it."
"If it had something similar to Microsoft’s DTS engine then it would be the best database system out there."
"It's difficult to make changes. It's a very complicated product in general — that's the issue."
"Their support could be better. There should be more visibility on the progress of the ticket, and their last line of support should be more knowledgeable. Other than that, we have nothing to complain about."
"When we are talking about event space architecture, scalability generally comes into play. For example, I might have a hundred thousand transactions a second, and then all of a sudden, I build something that everybody in the world wants. The next thing I know is that I have a million transactions a second. So, to be able to process the throughput, I'd have to scale up, and then when the holidays are over, I'm again down to a hundred thousand transactions, and I want to scale back down. SQL Server is not going to do that. In this way, it is not very scalable. One of the reasons why they want us to use Kafka is so that if we need to, we can do that, but our base program is on SQL Server. So, this is where we would use a Kafka event stack so that if I need more servers, I can just write a command, and I can have more consumers, more brokers, and more producers, and when the holiday season is over, it scales right back down again. SQL Server is not going to do that."
"You do need to have technical knowledge in order to install the solution. It's not something a layperson can do."
"Support could be improved."
"It would definitely be better if SQL Server were free."
"SQL could be improved by making all features available on the on-premise version of the product as well as the cloud version. When you buy the on-premise version, it's sort of an inferior product compared to the cloud version, which seems to get most of the latest and greatest features."
"The way SQL Server pivots data could be improved. For example, I would like built-in comma-separated pivot and unpivot functions."
MySQL is ranked 4th in Relational Databases Tools with 142 reviews while SQL Server is ranked 1st in Relational Databases Tools with 260 reviews. MySQL is rated 8.2, while SQL Server is rated 8.4. The top reviewer of MySQL writes "Good beginner base but it should have better support for backups". On the other hand, the top reviewer of SQL Server writes "Easy to use and provides good speed and data recovery". MySQL is most compared with Firebird SQL, PostgreSQL, MariaDB, Teradata and Oracle Database, whereas SQL Server is most compared with MariaDB, SAP HANA, Oracle Database, LocalDB and Vertica. See our MySQL vs. SQL Server report.
See our list of best Relational Databases Tools vendors.
We monitor all Relational Databases Tools reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.