RE: A SQL Server Log Reader – SQLServerCentral

SSC Guru

Points: 323504

October 24, 2012 at 2:02 pm

Jet-Ski (10/24/2012)
We actually had this just yesterday. Someone deleted 100 records from our CRM, told us about it 30 minutes later. We did a point in time restore, but lost 30 minutes of customer service cases and contact logs. It's less work adding those than it would have been to re-add the 100 contacts, but if we could have isolated just that transaction, it would have been nice.
Had they come to us the next day, they would have been SOL and would have had to re-add those contacts on their own.

couldn't you have done a point in time restore on As a new database, and simply scripted the 100 deleted contacts out as a SQL INSERT statements to run on production?

then the 30 minutes of data and the rework would not have been needed at all;

if your database is huge, it might be hard to do, what with trying to come up with space for another monster db, but that's a better method, i think.

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!