Yesterday, a customer of mine has his server computer completely frozen. He done a hard reset. But after opening the database again, the database was vastly corrupted and unusable. Is it possible that the corruption was due to the .journal rollback future, during the opening process ? I suspect so.
Last month another customer had a power outage. After opening the database again, the last 10 transactions (or so) were lost, despite the fact that I flush the database each time a task (transaction) is completed. Don't remember if the database was corrupted this time, sorry.
In order to avoid these problems. I plan to test the database before opening it, doing a database.CheckRollback.
1) backup the database
2) delete the .journal file
3) open the database
Could you give me an advice ? What is the right way ?