How to decide between mysql and SQL server?
-
I'm in my last year in college and creating an application for a company is a major requirement for my diploma. I will be using C# (MS Visual Studio) to create a transaction processing system with its own database. However, after doing some research, it seems that I'm still unable to decide which would be the better choice for the system I'm planning to create. Some say MySQL has more advantages, some say SQL Server does a better job at handling data for businesses. I can't seem to find any consensus. I've only had experience with MS Access, and a bit with MySQL for Web programming. To be honest, as of now I don't have a list yet of the specific requirements of the system since I will still have to meet with my advisers. It will however involve the basic functions of a common TPS: adding/deleting/editing data, viewing data, printing of reports, database management. There will be loads of data to be handled as this will be developed for business use. I am also planning to include an audit trail feature, so there's time-tracking involved. What would you advise? What I have tried: After looking up several articles on the internet I still can't decide which would handle the basic needs of a TPS better. Even some of my instructors have conflicting opinions on this; some advise me to use MySQL, some advise me to use SQL Server.
-
I'm in my last year in college and creating an application for a company is a major requirement for my diploma. I will be using C# (MS Visual Studio) to create a transaction processing system with its own database. However, after doing some research, it seems that I'm still unable to decide which would be the better choice for the system I'm planning to create. Some say MySQL has more advantages, some say SQL Server does a better job at handling data for businesses. I can't seem to find any consensus. I've only had experience with MS Access, and a bit with MySQL for Web programming. To be honest, as of now I don't have a list yet of the specific requirements of the system since I will still have to meet with my advisers. It will however involve the basic functions of a common TPS: adding/deleting/editing data, viewing data, printing of reports, database management. There will be loads of data to be handled as this will be developed for business use. I am also planning to include an audit trail feature, so there's time-tracking involved. What would you advise? What I have tried: After looking up several articles on the internet I still can't decide which would handle the basic needs of a TPS better. Even some of my instructors have conflicting opinions on this; some advise me to use MySQL, some advise me to use SQL Server.
-
But if you can live with the limitations, the price for SQL Express[^] is the same as the price for MySQL. :)
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
-
I'm in my last year in college and creating an application for a company is a major requirement for my diploma. I will be using C# (MS Visual Studio) to create a transaction processing system with its own database. However, after doing some research, it seems that I'm still unable to decide which would be the better choice for the system I'm planning to create. Some say MySQL has more advantages, some say SQL Server does a better job at handling data for businesses. I can't seem to find any consensus. I've only had experience with MS Access, and a bit with MySQL for Web programming. To be honest, as of now I don't have a list yet of the specific requirements of the system since I will still have to meet with my advisers. It will however involve the basic functions of a common TPS: adding/deleting/editing data, viewing data, printing of reports, database management. There will be loads of data to be handled as this will be developed for business use. I am also planning to include an audit trail feature, so there's time-tracking involved. What would you advise? What I have tried: After looking up several articles on the internet I still can't decide which would handle the basic needs of a TPS better. Even some of my instructors have conflicting opinions on this; some advise me to use MySQL, some advise me to use SQL Server.
I´m sorry to mess things up for you. But I have to recommend you have a look at Postgresql with Entity framework. It´s just awesome, very productive when writing code.
-
Yes, as much as possible I would like to stick to something that's free. I have MySQL Workbench, and SQL Server has an Express version.
-
I'm in my last year in college and creating an application for a company is a major requirement for my diploma. I will be using C# (MS Visual Studio) to create a transaction processing system with its own database. However, after doing some research, it seems that I'm still unable to decide which would be the better choice for the system I'm planning to create. Some say MySQL has more advantages, some say SQL Server does a better job at handling data for businesses. I can't seem to find any consensus. I've only had experience with MS Access, and a bit with MySQL for Web programming. To be honest, as of now I don't have a list yet of the specific requirements of the system since I will still have to meet with my advisers. It will however involve the basic functions of a common TPS: adding/deleting/editing data, viewing data, printing of reports, database management. There will be loads of data to be handled as this will be developed for business use. I am also planning to include an audit trail feature, so there's time-tracking involved. What would you advise? What I have tried: After looking up several articles on the internet I still can't decide which would handle the basic needs of a TPS better. Even some of my instructors have conflicting opinions on this; some advise me to use MySQL, some advise me to use SQL Server.
Nothing that you have described depends on a specific database. The question of SQL Server or MySQL therefore becomes a personal choice. And, in this setting, that's all it is - personal choice, normally shaped by personal experience. For the very common functionality that you describe, you will not see much advantage either way. In a real life business situation, the scenario changes. You would probably have the resources to do large-scale performance testing for your specific scenario, and could come to a factual conclusion that way. Or, more likely, your employer would dictate which database you were to use. But you're not in that environment. And it really does not matter. Here, it's on the same level as "Do you like blue cars or red ones?" Code your solution in such a way that the database logic remains in the database - stored procedures, functions, etc. That way, assuming that you are connecting by way of something like Entity Framework or even ADO.net, your C# code should be talking to your database's interface - calling specific procedures or function names, rather than relying on database-specific functionality. That way, it really does not matter which database provider you choose. So long as the entities you create within the database present themselves the same way, you can switch (for example) from SQL Server to MySQL to Oracle to Access easily. Make your application configurable, if you like. That way, a simple change to a config file can allow your application to switch databases. You'll rarely find a real life case that calls for that, but it might get you a few more points when you hand in your assignment! Good luck!
-
I have more experience with MySQL Workbench because I've done Web programming before, and initially I was already planning to go with it for my project since I'm more familiar with it. However, a schoolmate of mine also developed such TPS, an electoral system to be precise, and he used SQL Server for it, and he recommended it to me, and with all these different opinions it's hard for me to decide.
-
I´m sorry to mess things up for you. But I have to recommend you have a look at Postgresql with Entity framework. It´s just awesome, very productive when writing code.
-
I have more experience with MySQL Workbench because I've done Web programming before, and initially I was already planning to go with it for my project since I'm more familiar with it. However, a schoolmate of mine also developed such TPS, an electoral system to be precise, and he used SQL Server for it, and he recommended it to me, and with all these different opinions it's hard for me to decide.
To turn the question around a bit, which one do you want to have experience with?
Wrong is evil and must be defeated. - Jeff Ello
