Corrupted snapshot database
My snapshot database got totally hosed when I sorted it. I had over 30000
records in it. The sorted/corrupted version has 46,184. Virtually all of them
appear blank (no before and after icons). Many of them have "unknown user"
as the creator. Many of them are marked as private records.
Any idea on what happened and what I can do to avoid it in the future?
The backup of the snapshot database is c:\sqdata\sqproof\sqproof.dbu
To restore the backup copy of the database,
- delete the current snapshot database (c:\sqdata\sqproof.db); and then
- rename the backup (.dbu) to the current database (.db).
I don't know what the problem is or was. I haven't experienced any
problems in the last several years with sorting the snapshot database. I
regularly sort my snapshot database on three different computers.
General comments:
- If your data is important to you, then make regular backups!
- When a snapshot or getin/getout database is sorted, the original is saved as .dbu.
- When the list, parse, or abbreviation database is edited, the original is saved as .dbu.
- So... As long as you don't try sorting a corrupted database, you can
still retrieve the entire contents of the original.
The following files should occasionally be backed up:
- the snapshot database (c:\sqdata\sqproof\sqproof.db)
- the getout database (c:\sqdata\squaredb\getout.dat)
- your sequences (c:\sqdata\seq*.seq)
- the 'dates' databases (c:\sqdata\sqused\sqused.db1 and c:\sqdata\sqused\sqused.db2)
