Not to be well mean. But building a restore next to a prod DB and comparing data should be what we always do. I'm mean your just sewing together something that is missing. You can't very well roll back a DB to yesterday just because 16 rows where dumped. That would be well foolish.

I will say that I have had to do something similar to what your outlining about 5 times this year alone. One mistake by an analyst or developer can have you up all night. Should we lock them out of PROD, yes of course we do, but what I see in these events is someone drops code that deletes more then it should and once given the right well it can be misused. This can be very painful especially as I have one DB at 2 TB, and it's always an emergency to find a server admin to give me 2 TB of "temp" space as we are running out seems everyday.

the real problem though is people think you can just grab one table from a backup and don't understand you backup the whole data file not objects in DB's. They assume it's 5 minutes when it can take days to bring back and of course they have a deadline that they will now not meet. Ah the glamours life of a DBA.

As for Red gate they own this site so I won't suck up to much (free shwag? just ask for my address) but there backup program is awesome. You can restore just a table out of I think the professional one, but the cost has my management running for the hills. We tried the 14 day eval and it worked wonderfully. I hope they will drop the price a little in the future. I will also add that it isn't all that faster especially if it's a huge table spread across multiple datafiles, but from a not having to call a server admin for space standpoint I find it to be very useful.

Enjoy...