Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Before running backups on the data from an application I need to close it cleanly without risking an improper shutdown and data corruption in a Paradox Database.

How likely is that, if I use taskkill and force the process to close in a batch file? That is what I am planning but I wonder if I might face other problems as a result.

No one can ever seem to remember to shut the program down normally.

share|improve this question
Killing a task is the exact opposite of closing it down cleanly.. – pauska Oct 21 '10 at 2:01
Any suggestions on how to script a clean closing? – datatoo Oct 21 '10 at 15:49
up vote 2 down vote accepted

What corrupts databases are uncommited writes. I don't know how prone Paradox is to that kind of thing, but the sort of ungraceful shutdown taskkill does makes it much more likely to happen. If the application hasn't done anything in a while chances are good you'll get away with it, but you're GOING to hit corruption at some point.

share|improve this answer
thanks for that. I am getting corruption now when the application is left open indefinitely with unsaved images which it catalogs. – datatoo Oct 21 '10 at 15:17

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.