Thank God for rollback. Surely he didn't have auto-commit on!
A very real problem I ran into in SSMS was I had inadvertently highlighted all parts of the script except the "where" clause and executed it. I thought to myself, "why is this taking so long for such a low impact change?"
I knew running ad-hoc scripts in a production environment was risky, but I accepted it. We had a fresh enough backup already loaded in our sandbox environment and the removed data was quickly restored from there after some cursing and some quick hacking. This happened 6 years ago.
The data that was deleted? All the user accounts of our biggest client. This happened at 10 AM in the morning on a weekday. FML. I was lucky to keep my job.
As an aside, if you do something on my level of stupid, then escalate the issue up the chain of command as quickly as possible. Do not hide it. If you've built up enough good will with your co-workers and bosses, they will rally to your aid. Definitely don't try to hide it. That will almost certainly lead to termination.
Check my war wounds. Every soldier has a story to tell.
Always use transactions
10 AM in the morning
good thing it didn't happen at 10 AM at night, I guess
It was right after 9 in the afternoon and my eyes were the size of the moon.
Let's say I was once very happy that I remembered learning about a certain Oracle feature called flashback queries one day when I made that mistake.
Sudo rm -f / home/beth/Pictures/SaturdayNight.jpg
Why would you even need Sudo, let alone the force flag to delete a file from your home folder
To feel powerful
Where clauses should be syntactically required for delete or update statements. Throw an error without them. If you really want to hit every record in the table then throw a WHERE true in there just to be explicit.
Its such a common mistake i dont get why this isnt a thing.
Good idea.
Easy enough to slap a where 1=1; on there if you want to burn the place down
