How to decide between mysql and SQL server?

Question

2.00/5 (2 votes)

See more:

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.

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.

Posted 13-May-16 0:44am

kmllev

Updated 13-May-16 1:36am

Add a Solution

Comments

CHill60 13-May-16 6:55am

Cost? SQL Server Express is free ... that would swing me everytime ;-)

Garth J Lancaster 13-May-16 20:45pm

yeah - thats one consideration - and for a college app, it should be more than capable (I forget what the 'limits' of Express are)

CHill60 15-May-16 13:09pm

From memory you can use it commercially too. Not about the Community Edition though which has a few extra bells and whistles

3 solutions

Solution 1

This is a question that is likely to generate opinions and is not really suited for the Quick Answer forum.

Post it in this forum instead: Database Discussion Boards - CodeProject[^]

It is not a bad question, just the wrong forum.

Posted 13-May-16 0:50am

George Jonsson

Comments

kmllev 13-May-16 7:07am

Oh, I see. My bad. I'll move it. :)

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Garth J Lancaster · Accepted Answer · 2016-05-13T00:52:00

Solution 2

You list absolutely no requirements of your system/program that we could look at and go 'ah huh, that points to x vs y'

I would design a data layer that was independent of the database underneath anyway (which is consistent with modern approaches to layers anyway) - I find it hard to imaging, but should you find [god knows what] situation where you need to switch db layers you can then do so

Posted 13-May-16 0:52am

Garth J Lancaster

Comments

kmllev 13-May-16 7:21am

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.

Garth J Lancaster 13-May-16 8:17am

I think you need to figure out what your program needs to do (requirements) eg

'Price'
Support
CRUD
Stored Procedures
X
Y
Ease of Deployment
Maintenance
?? Dave's Comments

and have two columns, MySQL, SQL Server

and if you end up with ticks in one and not the other, thats the way you go - nothing wrong with Dave's advice if he's been following 'trends' more than I have

kmllev 13-May-16 8:23am

Thank you, I will keep those things in mind. :) I will accept Dave's solution for now. :)

Sergey Alexandrovich Kryukov 13-May-16 8:30am

5ed.
—SA

Dave Kreskowiak · Accepted Answer · 2016-05-13T01:36:00

Solution 3

SQL Server.

The way Oracle is handling Java and MySQL, it's future is ... in doubt. Well, at least as an Oracle project anyway. If Oracle finally decides to give up MySQL it'll most likely go back to being a community open source project instead of one lead by Oracle.

But that's just my humble opinion. If you want to put the life blood of your company on a project with a bit of shaky future, go ahead.

Posted 13-May-16 1:36am

Dave Kreskowiak

Comments

Sergey Alexandrovich Kryukov 13-May-16 8:36am

Good point. It sounds troublesome, so could you elaborate on that? What is "the way Oracle is handling", what are some bad signs?

Such concerns already caused creation of the forks, such as MariaDB: https://en.wikipedia.org/wiki/MariaDB.

—SA

Dave Kreskowiak 13-May-16 9:48am

The exodus of open source developers for it. Oracle doesn't have a problem with the number of users using it, just the number of developers writing for it. Those numbers of been dropping ever since Oracle bought Sun and all the open source projects they had, including MySQL.

Sergey Alexandrovich Kryukov 13-May-16 17:38pm

Oh, I understand. It really sounds troublesome, really. It's interesting that less people work or are willing to work at the same work on commercial basics, but it might be because Oracle is not willing to invest decent money in this work or act unfairly to the developers.

It's very indicative that the original MySQL creator Michael Widenius, one of MySQL founder, quit MySQL and now leads MariaDB. What do you think about the prospects of MariaDB then?

Anyway, thank you very much for sharing your view on this matter.

—SA