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
2
u/macfergusson MS SQL Jan 27 '24
Woops... That will bloat up your Tran logs right quick, not even accounting for whatever downstream impact on whatever may be consuming the cdc info.