Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
lorentz1572618h@Lensflare Supposedly, they actually went around advertising MSSQL to executives when they first got into the DB business to get it off the ground. The fact that an executive listens to an external salesman for anything other than management tools is insane.
-
PaperTrail1045817h> "How is MSSQL so popular?"
#1, its from Microsoft (nobody ever gets fired when choosing a product from Microsoft)
#2, its not Oracle
#3, Bill's nearsighted grandma with dementia can create a table with as much skill as MS Certified DBA.
I've been using MSSQL since 6.5 and like any legacy 'enterprise' product, its become so bloated with nonsense nobody but niche edge cases every use its 'enterprise' features.
Related Rants
-
Aiei16Manager: Hey, this is Junior. he will work with you from now on. Me: Oh cool, we could use some help. (moments...
-
PonySlaystation10You know your week starts great, when you receive a call, that the whole shop database of a company is not wor...
-
socialdeveloper16
We all have that kind of friend who is losing his shit , screaming , swearing , crying , whenever the code doe...
How is MSSQL so popular? "Oh yeah, sometimes you have to use dynamic SQL because the compiler doesn't correctly detect the impact of DDL commands and rejects working code" god fucking what? Why does the compiler infer the future structure of tables after a DDL command if it can't do so reliably? In my world, if it becomes public knowledge that a compiler incorrectly infers something, the maintainer scrambles to remove the inference instead.
I also find it surreal that I have to disengage versioning on a table in order to be able to modify the version history. Like surely, there should be a mechanism to temporarily skip the hooks other than ALTERing the table into a regular unversioned database table and then ALTERing it back, rebuilding the versioning infrastructure from scratch. SQL is awful and MSSQL is doubly awful.
rant
madness
mssql