If dropping a database scares you, you are either unaware of the disaster recovery process, or there isn't one. Edumacate yourself, or the org, as appropriate, so as to increase your confidence when dropping databases.
On a related note, a lot of companies establish recovery processes without actually testing them. Then the first time a recovery is needed they find out that it doesn't work as expected.
I wasn't prepared to be personally attacked like this.
And also not updating them when things change. The recovery process for a database changes considerably once it's involved in replication, which one client found out the hard way.
indeed
I'm going to be a junior soon. Thanks for the heads-up not do this 🤦🏽♂️
No, the message is: you might do this and don't worry, you'll be fine :-)
My protip for juniors and databases... never modify the production database and always use bound parameters.
If junior gets write access to prod that's on whoever gave them that access
They put de niro twice? :) Or 3 times, top left is him too?
This meme works in multiple ways, and I've worked in at least two of them.
Why would you do that? It sounds unpleasant.
Post funny things about programming here! (Or just rant about your favourite programming language.)
