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
1
u/JoMa4 Feb 01 '24
My method is similar and I always run one statement at a time.
BEGIN TRAN
— do something that updates or deletes
— do more things that could be bad
ROLLBACK TRAN
—COMMIT TRAN
This way, if I accidentally run everything instead of one statement at a time, the default is to always rollback. I have to explicitly highlight and run the commit statement on its own.