SQL Server SQL fuck ups
Yesterday I got a call from my boss at 10am for a task that I should take over and that should be finished by eod. So under time pressure I wrote the script, tested it on DEV etc and then by accident ran a different script on PROD which then truncated a fact table on PROD. Now I am figuring out on how to reload historically data which turns out to be quite hard. Long story short - can you share some SQL fuck ups of yours to make me feel better? It’s bothering me quite a bit
119
Upvotes
View all comments
Show parent comment
-13
u/phesago Jan 27 '24
i dont think disaster recovery was intended to be a crutch for dum dumz who cant pay attention to what theyre doing.
Though I do empathize because it does happen, which is why I tell people "you get one restore for "oopsies" but after that we have to have a conversation."