views:

1530

answers:

3

I intend to start developing an ASP.NET application and I am wondering which database to use. Performance is very important and the database should be able to handle without issues a database of about 50GB. I am wondering however, if a SQL Server license is worth paying for. I have looked for performance and scalability comparisons between MSSQL Server (2005/2008) and MySQL but I can't seem to find any good tests. Can you point me to some extensive benchmarks related to this subject?

A: 

"The best choice depends on the situation"

See this article: MySQL or SQL Server

Mitch Wheat
I know the article, but it doesn't really help. I'm looking for numbers, performance and scalability charts.
iulianchira
+5  A: 

MySQL traditionally is very fast if you are doing a lot of reads. For example in a web site there is probably a 100 to 1 read write ratio so MySQL works well. If you are planning a high transaction database then head straight to MSSQL. If money is no issue head straight to MSSQL anyway because it is a better product.

Craig
+1  A: 

As mentioned, MySQL can provide high read performance (assuming simple queries with few or no joins) as long as you use the default table type.

However you also stated the database is 50GB in size, which suggests you may be looking for a database that will reliably store the information. Using the default table type MySQL is not a reliable database by any stretch of the imagination.

If you want a fast, free alternative to MS SQL then PostgreSQL may be a good choice - it is fast reliable, and has a more open licence (if you use MySQL for a commercial project you'll want to read its dual licence very carefully). The only downside to PostgreSQL is that it shares some of the same DBA guru requirements as Oracle, where as MS SQL can often be managed by a regular IT person, and MySQL doesn't need much management besides restoring the old backups everytime it decides to become corrupted and lose your data.

David
"become corrupted and lose data" doesn't sound good at all to be honest, and from my experience with MySQL there are reliability problems. I know about PostgreSQL, but I have very little experience using it, and again to consider it as an option I need to see some performance tests.
iulianchira