Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What options are available for rolling back transactions after the fact in SQL Server?
I’m looking to have a plan in place before somebody deletes 10,000 of the wrong rows.
I’m sure there used to be more. Back when I was a prod DBA I couldn’t get through a week without some irritating Sales muppet trying to flog me a GUI or tool.
I would also suggest you take regular backups with FULL recovery. A 10k rows update may have subsequent changes that will invalidate any rollback.
FWIW, I’ve never seen the need for one. No-one can delete 10k rows in my DB anyway unless it’s designed that way: why would I allow someone to run DELETE directly?