MySQL over Microsoft SQL Server{3}

After several hours of reading Microsoft support articles on how to install Microsoft SQL Server 2008 on my machine, I finally got everything to work.  However, for the amount of time sacrificed I wanted to find some significant differences between MySQL and Microsoft SQL Server.  To my surprise, I found out that MySQL 5.1(150MB) is about the same size as Microsoft’s  .NET framework,  a necessary component in the installation of  Microsoft SQL Server 2008(2GB). A possibly bias article entitled “Why Move to MySQL from Microsoft SQL Server” written by one of MySQL’s director Robert Schamuer,  makes a strong case for MySQL.

The article does not hesitate to compare the installation time of Microsoft SQL Server to MySQL. In less than 15 minutes you can download, install, and start working on your MySQL database project. I wish the same applied for Microsoft SQL Server 2008, but unfortunately Microsoft SQL Server fails miserably in this category. Okay, maybe the wait is well-warranted because a larger file usually means more/better features.  However, the author points out that a big file doesn’t always translate to more features or better performance.  MySQL actually has more features because it is open-source, available on many platforms, and has a pluggable storage engine architecture.  Many DBA’s  admire the flexibility offered with MySQL’s support for different storage engines. This means that a DBA can have both transactional and non-transactional tables with a degree of ease.  MySQL also supports different types of partitioning(range, hash, key, list) whereas SQL Server only offers range partitioning.   The article does mention that Microsoft SQL Server offers better security, optimization,  and data auditing abilities.

Summary from article:

The reason I chose this article is because I was very frustrated with the installation process of Microsoft SQL server. I also came across a helpful website that allows aspiring Database workers to demonstrate their knowledge through solving a handful of exercises that challenge your ability manipulate data through statements. Or it could just serve as a good review for our project and upcoming exam. Some exercises incorporate MySQL 5.5 while others use SQL Server 2008 R2, thus I had to know the differences between the two. After reading the article,  I was more impressed with MySQL for the reasons outlined in the table above. Maybe is about time CPP starts transitioning away from Microsoft products and into the main-stream arena. Also, the website I came across for learning SQL: .

Schumacher, R. (n.d.). MySQL :: Why Move to MySQL from Microsoft SQL Server?. MySQL :: Developer Zone. Retrieved November 12, 2012, from