Mysql vs. Sql Server - who wins?
I would venture to start a holivar topic :)
I think everyone will agree that, by the Mysql functional, Sql Server significantly loses. In my opinion, Mysql does not win by the criterion of free: Sql Server has a free Express version, which, unlike a competitor, can be used in commercial development without licensing restrictions.
But now it's not about that. For me, the most interesting was the question of performance. Tests from manufacturers believe difficult, so I decided to conduct my own test.
To do this, I took the AdventureWorks database and overtook it in Mysql (I got a dump of about 100 MB in size) with all the keys, indexes, etc. saved. After that, I wrote a test application on .Net that would drive the same database queries, and you can vary the number of concurrent threads. Inquiries were substituted for random numeric and string values (in conditions of where, order by, etc.) so that they are not cached. No optimizations were performed on any of the servers.
Well, let's go straight to the point :)
Simple SELECT queries (with where, order by, limit / top conditions):
Complex SELECT queries (with various join, nested queries):
There are no insert / delete / update requests, no triggers or stored procedures. And while there are no sources of the program itself, database dumps, etc. All this needs to be made out, but if it's interesting, I'll do it :)
I think everyone will agree that, by the Mysql functional, Sql Server significantly loses. In my opinion, Mysql does not win by the criterion of free: Sql Server has a free Express version, which, unlike a competitor, can be used in commercial development without licensing restrictions.
But now it's not about that. For me, the most interesting was the question of performance. Tests from manufacturers believe difficult, so I decided to conduct my own test.
To do this, I took the AdventureWorks database and overtook it in Mysql (I got a dump of about 100 MB in size) with all the keys, indexes, etc. saved. After that, I wrote a test application on .Net that would drive the same database queries, and you can vary the number of concurrent threads. Inquiries were substituted for random numeric and string values (in conditions of where, order by, etc.) so that they are not cached. No optimizations were performed on any of the servers.
Well, let's go straight to the point :)
Simple SELECT queries (with where, order by, limit / top conditions):
Complex SELECT queries (with various join, nested queries):
There are no insert / delete / update requests, no triggers or stored procedures. And while there are no sources of the program itself, database dumps, etc. All this needs to be made out, but if it's interesting, I'll do it :)
')
Source: https://habr.com/ru/post/82553/
All Articles