>Thanks Hilmar, will definitely try out your suggestions.
>However, this approach has its risks in that if there's a power failure (with no UPS), it could result in serious data corruption.
>Yau
I don't know why this particular approach should be especially prone to data corruption.
Anyway, to avoid data corruption, I recommend:
1) I will assume you use buffering. After each TableUpdate(), you should give the command FLUSH to empty the buffers oat the operating system level.
2) Make sure write-cache is disabled on the file server (that is, the place where your data files are stored).
3) And, of course, make frequent backups.
In Bata-Bolivia, during 3 years I had to reindex only 3-4 times. I never had problems with the data itself.
HTH,
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
