there's a difference between a developer having access to a production environment account that has production rights vs. giving the normal developer's normal account that he/she uses every day production rights.
I don't use sql server but there's definitely something fishy about the above situation. And this statement is straight up false:
The only way is DISCIPLINE.
Relying on developers to "be careful" is how that database got deleted in the first place. You are supposed to build systems with the expectation that humans will screw up, no matter how disciplined your team is.
Umm, that's why you set up permissions on production. And although I'm a developer... never give developers production rights.
In the world of devops, developers typically do have production rights. Still, it shouldn't be that easy to access them in the way OP mentions.
there's a difference between a developer having access to a production environment account that has production rights vs. giving the normal developer's normal account that he/she uses every day production rights.
I don't use sql server but there's definitely something fishy about the above situation. And this statement is straight up false:
Relying on developers to "be careful" is how that database got deleted in the first place. You are supposed to build systems with the expectation that humans will screw up, no matter how disciplined your team is.
Exactly. Security 101.
Lel, would you like to say that you even don't fix bugs right on production servers via FTP?
Well, that depends.
If it's a client side issue - I prefer clicking F12 and changing through the dev console :-)