I’m a software engineer and Microsoft’s development ecosystem has been amazing since they started redoing everything with dotnet core etc.. I wouldn’t blame the tech stack for this.
I had to work with SQL some 20 years ago (one of the many little turns my career has taken). It was very frustrating - commands that didn't work, or didn't work as described, or gave a different result. Now I wonder if that wasn't by design - so they could become undocumented features of the SW?
I mean it could have been just bad SW, like so many things Micro$uck, but it could also have been a way to slip code past people for "other" use.
A couple other people I knew encountered the same issues I did. It may have been a specific release and certain commands - IDK. Most of the commands were fine.
I’m a software engineer and Microsoft’s development ecosystem has been amazing since they started redoing everything with dotnet core etc.. I wouldn’t blame the tech stack for this.
A system is only as secure as the architects make it.
I had to work with SQL some 20 years ago (one of the many little turns my career has taken). It was very frustrating - commands that didn't work, or didn't work as described, or gave a different result. Now I wonder if that wasn't by design - so they could become undocumented features of the SW?
I mean it could have been just bad SW, like so many things Micro$uck, but it could also have been a way to slip code past people for "other" use.
I've been using MSSQL for over 25 years. Never had an issue with it.
A couple other people I knew encountered the same issues I did. It may have been a specific release and certain commands - IDK. Most of the commands were fine.