Ed Wagner (12/25/2015)
Anders Pedersen (12/25/2015)
Since the article was reposted...
Two of the largest credit charge clearing systems runs on SQL, and has for a long time. The first time I worked on it, it was on SQL 2000. Mission critical, tons of transactions per second (sorry was not operational on either so don't know the numbers).
Eve Online runs on SQL, logging pretty much everything that goes on in the game (with 50k+ players online on the same world). They have some pretty interesting write ups on their blog about their SQL system).
A certain large phone company ran out of drive letters storing all their call records in SQL (one of the reasons we now have mount points).
A lot of very large companies use SQL Server to store a lot of data. SQL Server performs well for most tasks if done correctly. It's always possible to write inefficient code.
To that end, here's one of the most important things from the article....
From the article:
Over the years I've heard regular complaints and concerns from executives about SQL Server scalability.
I've found, over the years, that those very executives are actually a very serious part of the problem because they don't understand that databases (relational or otherwise) are NOT just a place to store data and so they "go cheap" when hiring people. They still think that the average front-end programmer with "good experience in SQL" (according the job description) is good enough. They don't realize how important it is to have at least one true "SQL Ninja" on the Team and, when they finally do make that realization, they don't understand that the idiot they just hired with supposedly 10 years of experience isn't actually an "SQL Ninja" nor even a qualified advanced user because they don't actually know what it takes to find and hire such a person. They also don't realize the train-wreck that their databases are in is because they didn't hire such an "SQL Ninja" long before the first requirement popped into someone's head and then wonder why such a person frequently says, "Damn... this isn't going to be easy, folks".
All C-Level managers with even one computer on site should make a new year's resolution to first seriously educate themselves, learn how to write the right kind of job descriptions, and then learn how to properly conduct both phone and in-person interviews to protect the company from the thousands of applicants out there that don't actually have a clue despite what their sometimes-outright-lie-of-a-resume claims before they go bad mouthing any database product, especially SQL Server. They also need to learn what an "alternative system zealot" and "new shiny object zealot" is and avoid them like the plague so they don't end up with the mostly unsupportable "Tower of Babel" that I've seen at so many companies fall pretty to.
Let's make 2016 the year that the vicious and unprofitable circle of ignorance ends.