>>For a backup, another option might be to do it at night - provided nobody is working. With Windows Task Scheduler, you can do this automatically - no need for anybody to be in the office.
>
>We do backups at night automatically. I know you are trying to help, but I'm not sure you are reading my posts fully.
Probably not.
> We have a process that needs to run after investment files come in during the night. After that process completes, only then can we run the one that copies the files.
OK, I didn't understand that was a prerequisite.
>>Yet another option is to use triggers to copy all changes to a secondary table, while it is being created - similar to an audit trail. From this audit trail - provided it is in an appropriate format - you can then reconstruct the backup. Accessing the audit trail is more reliable, since data will be added sequentially (all changes will be appended to the end).
>
>Good idea, and that's actually on our list. For the short term we're just trying to find a way to prevent the corruptions.
I don't know whether this is possible, but do you FLUSH your data after saving it?
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)
