well then maybe you need to talk to some of the bigger sites out there that refuse to use MSSQL for web based applications, apparently they didnt get the memo, whether you have 16Gb or 32Gb of ram, doesnt change the fact that MSSQL server will use almost twice as much resources as MySQL will, thus forcing larger applications to use servers dedicated to ONLY the MSSQL server, meaning that the application its self will have to sit on a different server accessing the db via the local network, that with human error kinda cripples any added security that MSSQL could have.
MySQL runs lightning fast on 4Gb of ram, on win server 2003 SP1. MSSQL runs the same with 16Gb on 2008 oO - not sure if you were proving my point or yours. . .
MySQL has built in security functions that MSSQL doesnt have: just as an example, mysql_real_escape_string - MSSQL doesnt have this, you can make it do something similar if you want to make a function for it in your db ( i personally will envoke both so i can use the added features of MySQL with my php and MSSQL, best of both ;) )
as an example, Craigslist uses MySQL only, used worldwide, nvr has down time, nvr had security issues, and apparently seems to do perfectly fine
dekaron uses MSSQL, they get hacked annually sometimes more than once, and have since before BMR (and yes, i am aware its human error that makes the security breech possible, but thats part of my point).
on that same note, most of all java applications will use MySQL, and java runs ALOT of things, yes i know they are owned by the same company, but they bought MySQL for a reason, they could just as easily used MSSQL.
im not trying to say what you are saying is wrong by any means, but saying you taught db admin classes doesnt make you an expert, but teachers teach what they know, usually with information from material and ppl with bias concepts of what the standard may be at the time, we are taught things that are incorrect from elementary school all the way in to college, most of the history we are taught is flawed, yet its the standard, and altho the ppl that teach those courses may be experts in what they are teaching, it doesnt mean what they are teaching is accurate in any form.
there is a reason why MSSQL isnt used as much as it should be, and on that same note, there is a reason why MySQL is used as much as it is, they both have their place where their usage is justified over the other, my point was that unless he is running a multi billion dollar fortune 500 company and has tried both avenues and came to the conclusion that MSSQL offers what is best for his company after carefully picking thru each pro and con, its not fair to just call MySQL shit, especially considering that function and syntax is all but similar and that his obvious lack of experience with both instances really doesnt allow such a blatant and grossly inaccurate judgement to be thrown around like which restaurant has the better cheeseburger
i based my opinion on the experience i have had with both over the years, ease of use and setup, cost, reliability, functionality, functionality and use of third party software like PHP and apache (both have massive support for MySQL but hardly any for MSSQL), and from my many years of experience seems like a simple choice; do i want a massive headache, or do i not.
