Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
DOS based PARADOX 4.5 DATABASE maintainance
- Thread starter Hpatel
- Start date
Not really.
However, if you have huge amount of data and there are a lot of adding and deleting actions. You may want to test and make sure your tables are not corrupted, regularly.
I used to use TUtility to verfiy the data at least once a week, mainly over the weekend. This is done unattented with a program, of course. So that, on Monday I could take care of any data corruption and prevent any further problem.
If there are not many tables, you could do this manually.
However, if you have huge amount of data and there are a lot of adding and deleting actions. You may want to test and make sure your tables are not corrupted, regularly.
I used to use TUtility to verfiy the data at least once a week, mainly over the weekend. This is done unattented with a program, of course. So that, on Monday I could take care of any data corruption and prevent any further problem.
If there are not many tables, you could do this manually.
We've been using Paradox DOS from v3.5 in 1992, to v4.0 in 1994 which we are still using. We've got approx 400Mb of data, largest table about 30Mb, next 15Mb. We've got about 10-15 concurrent users, on a Novell network and Win98.
We have a process that we run once weekly, which queries the data from all important tables, empties the table then adds the data back. This "packs" the table to it's smallest size. This I think, was suggested by Borland years ago.
Over the years there have been a few problems with damaged tables, but nothing too serious or common. I think the above process helps a little, just keeping the tables to minimum size. Generally, our experience has been pretty good, without doing much housekeeping.
Phil
We have a process that we run once weekly, which queries the data from all important tables, empties the table then adds the data back. This "packs" the table to it's smallest size. This I think, was suggested by Borland years ago.
Over the years there have been a few problems with damaged tables, but nothing too serious or common. I think the above process helps a little, just keeping the tables to minimum size. Generally, our experience has been pretty good, without doing much housekeeping.
Phil
- Status
Similar threads
- Locked
- Helpful tip
- Locked
- Question