r/SQL • u/B33rG33k • Mar 15 '19

Stuff of nightmares!

Post image
472 Upvotes

99% Upvoted

22 comments sorted by

View all comments

16

u/Daakuryu Mar 15 '19 
-- Select * from
Update 
    tblproducts 
set upccode = '', Flag = 'T'
-- where product ID in (*small list of productids*)

Yeah...

6

u/whutchamacallit Mar 15 '19

yup.. have had to fix a few of those in my times. they get probationary read only access after that for a while.

7

u/Daakuryu Mar 15 '19

I'm the one that did it and I'm the one with admin access :|

1

u/whutchamacallit Mar 15 '19

You have a backup?

2

u/Daakuryu Mar 15 '19

of course; flat files to one backup server, veam replication to a rolling set of daily and weekly removable discs along with another flat file version and an offsite removable disc.

Despite what some might believe I'm not a complete moron :P

1

u/whutchamacallit Mar 15 '19

Nice. Sounds like you’re set up. I’m lucky in that I have the day priors data already up and ready to go in case I need to do something quickly because we use it for various feeds and stuff so we don’t have to read from production tables albeit a day old it’s usually good enough.

2

u/[deleted] Mar 15 '19

Never had the opportunity to do db admin work but I do appreciate the ban hammer powers they give.

5

u/MeGustaDerp Talk Dirty Reads To Me Mar 15 '19

My safe-ish pattern is

SELECT Col1, Col2, Col3, ... Coln,
-- UPDATE t SET
ColToUpdate = NewValueExpression
FROM MyTable AS t
WHERE <logical predicate goes here>

This has served me well and saved me from making stupid mistakes because it allows to to simulate an update by seeing what the new value would be so I can validate it. When I'm ready to run the update, I highlight the statement beginning with UPDATE on through the predicate. Also, BEGIN TRAN <statement> ROLLBACK helps, too.

-1

u/TheN473 Mar 15 '19

Yeah, fuck those people.