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.
解决方案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
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.
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.