I know that few times DELETE command in SQL can be dangerous when used on the master Databases. I have done a couple of times (It was horrible) and would like to know how was your experience dealing with that?
I backup my local test database at least once a week, and all my connections to shared (test) databases are select-only until I've made sure I want to change something. Been able to prevent any serious update/delete problems so far. I'd recommend the read-only mode to anyone.
As a rule I always run DML sql statements within a Transaction using BEGIN TRAN when Creating, Updating & especially Deleting data to make sure that any changes can be easily rolled back. Using DELETE should never be an issue as long as you are careful and allow for roll back and even backing up data in case something goes wrong.
Arsh Multani
Software engineer & Founder @ SynSwift
I never had yet any horrible experience with that, but i would say that, i would for my own peace of mind , i will just run the SELECT example of DELETE query , and then be sure that it shows the result of which rows i really wanted to remove, if it's fine , then i just change SELECT * FROM to DELETE FROM ...