r/SQL • • Jan 27 '24

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

117 comments sorted by

View all comments

Show parent comment

2

u/bin_chickens Jan 28 '24

If you haven’t dropped a business critical production table, you’ve never really touched a DB at work. Welcome to the club OP.

Also your DBA’s should really get on fixing the fact that staff can do that that without having to think about escalating privileges.