I have been tasked with moving from a MSSQL backed database, entity framework co

Question

I have been tasked with moving from a MSSQL backed database, entity framework code-first, wcf service based MVC application to a MySQL backed database.

I have had being trying to find a performance comparison of entity frameworks with MySQL vs MSSQL but have yet to come across one.

Has anyone had and experience in this switch (either direction) ?
Was there any noticeable difference in performance after the switch ?
Was the generated SQL drastically different i.e was there loads of horrendous nested sub-queries instead of obvious joins in select statements after the switch
Motivation for DB change

The system I am talking about is our core platform. We have around 10 other sub-systems (all running PHP and MySQL databases). The thinking behind this, was that we should move everything to an AWS RDS MySQL instance.

I loathe this idea and am looking for technical reasons to stay on MSSQL. Our layers are very loosely coupled so moving over won't be much of a problem unfortunately.

Explanation / Answer

My company is currently in the middle of a migration from MSSQL to MySQL for one of our clients, involving approximately 1.3GB of data. Unfortunately I don't have straight performance comparisons because we're simultaneously reimplementing the existing ASP classic + c# service layer (both of which use hand-coded sql) to Java + Hibernate. To be honest, we're seeing better performance in the new version, but that's mostly because the old version was badly designed.

In the end, though, there really isn't that much difference between the two databases. MySQL has come along nicely in recent years and is now a fully-functional (if slightly quirky) database server.

Related Questions

Navigate

• Browse (All)
• Browse I
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.