[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1080
  • Last Modified:

What is the advantages and disadvantages of using MySQL instead if SQL Server?

What is the advantages and disadvantages of using MySQL instead if SQL Server?  If a specific software recommends SQL Server, what would be the disadvantage of using MYSQL instead?
2 Solutions
Under the General Public License, MySQL is an open source system. Without spending any amount, a developer can start working with this system. But a person needs to buy a commercial license if he wants to sell the software. But the case is bit different for MS SQL. A developer has to secure a license. For simple development purpose, a free SQL server is given. But if one wishes to use it for commercial purpose, then he has to purchase at least the Standard Edition of SQL server.

The MS SQL is a closed source compared to MySQL. The latter is available as an open-source and is thus easily accessible. For the MS SQL, one is limited within the Sybase-derived engine. But MySQL offers numerous variations like Heap, Berkeley DB, MyISAM, InnoDB etc.

If the two systems are compared on the basis of their performance, then it will be seen that MySQL surely has more advantages. It takes a very less storage space in the disk and the MyISAM database gives remarkable performance. Besides Windows, this system also performs well on UNIX and LINUX systems. For MS SQL, its performance is comparatively complex. It is difficult to work with it without very sound knowledge and efficient hardware. Working with MS SQL takes up more disk space compared to MySQL.

Compared to MS SQL, most of the foreign keys are not supported by MySQL. Some of the relational features found in MS SQL are missing in MySQL.

If the two systems are considered on the basis of recovery process, then SQL has more benefits than MySQL. Since it has a configuration with MyISAM, it sometimes becomes a drawback for the system. If there is a disturbance or interruption takes place while working with MySQL, then it may result to loss of data. Even if the system faces any problem while working with MS SQL the data is not lost.

Both MySQL and MS SQL adopt ample security measures from the very beginning. If a port becomes too vulnerable to use then the user is allowed to change it. The user is required to update the software from time to time to protect them from unwanted users and intruders
Using rkpanidarapu's very excellent comparison of the two databases, it sounds like a no-brainer to me in favor of MS SQL, when you compare only the most important features:
1. As for storage space, who cares? As big and cheap as hard drives are today, database size isn't a big concern.
2. MS SQL might be more difficult to work with, but I believe it is the more popular and used database, and a wealth of info exists out there to solve any problem you'd run into.
But now for the BIG reasons:
3. Most foreign keys and some relational features are not available in MySQL.
4. The "recovery process" issue in his next-to-last paragraph puts the nail in the coffin for  me...a disturbance or interruption will cause MySQL to lose data, whereas MS SQL will not. Do you want to EVER lose data? I rest my case.
About the licensing issue, we use MS SQL Express, which is free to both us and our customers. No money needed.
One significant correction to the two previous answers. MySQL DOES support foreign keys when the InnoDB engine is used.


Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now