|
bax
Junior Member
141 Posts |
 Posted - 18 September 2002 : 23:16:42
|
Ouch. One thing you could try - restore the database as something different - Forum_2 or something like that (I'm assuming SQL). Then, you could write a query to move the data from this database to the other. Depends how much traffic, how much loss you have if it is worth it.
One other suggestion - create backlogs to handle events like this. I've created a way so that when you delete stuff (again, with SQL Server only), it logs all of the deletions to a set of backlog tables. Makes the database quite a bit larger, yes, but protects from situations like this. By logging all deletions, I can just go to the backlog and restore from there, without having to go thru this. If you want input on this, email me. |
 |
|
Topic Locked
