Introduction To Maintenance
Collect! is a business application database. As you grow,
Collect! becomes more and more important to you. It is
all your business data, the life of your company.
This is more crucial than your letter templates in Work
or your address book of phone numbers. Without Collect!
up and running, you are virtually out of business. So it is
essential that you keep your Collect! database error free
and fully functional.
With any application of this size and importance, it is
important that either you, or your technician, maintain the
database. On a regular basis, Collect!'s internal maintenance
routines should be run to keep your system in top shape.
As well, for those more technically inclined, Collect! can
be maintained by external methods.
Both methods can be customized to efficiently maintain your
database. Larger databases may use more resources to keep
in shape. Using the external database maintenance method,
your technicians can fine-tune exactly the parts of the database
that need the most attention.
If you neglect routine database maintenance, this will inevitably
catch up with you and may result in serious data loss.
We recommend you backup critical data files before running
maintenance since, if the machine is failing, the maintenance,
while manipulating data files, may cause undesirable
consequences and, potentially, loss of data.
Please refer to Backup Database Topics for options
for backing up your files.
See Also
- Database Maintenance Topics
|
Was this page helpful? Do you have any comments on this document? Can we make it better? If so how may we improve this page.
Please click this link to send us your comments: helpinfo@collect.org