In order to restore with litespeed you would have had to backed the db up with litespeed. mutley is correct. The only way is to restore the database to another server and restore the table you need. However, I should caution you on doing just one table. You could cause data integrity problems if there are FK relationships with other tables.
If you have the transaction log from a time frame when the table was good. you may be able to use a tool like lumigent log explorer to undo the bad transaction.
- Paul
- If at first you don't succeed, find out if the loser gets anything.
You can also possibly look at your backup and recovery plan a bit closer to prevent these things. If you have tables that are business critical (not that the entire DB isn't) you can set up file groups for high transactional tables.
This probably should have been done in the first place on a DB that size for performance reasons alone.
If anything I hope you take this event and better the planning for these in the future
____________ signature below ______________
You are a amateur developer until you realize all your code sucks.
Jeff Atwood
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.