Because your database needs regular maintenance to keep running in mint condition ... just like your car. Most importantly, following this maintenance program regularly will assure you that your database is being backed up. And just like your car, you can do the maintenance yourself, or we can help you for $125. Simply
Training Solutions 17-Step Database Maintenance Program
1. Document current ACT! version, Service Pack, and Hotfix. Determine if more current ones are available and if they should be installed.
2. Document active and inactive users and their security roles. Determine if there are at least two ACT! Administrators in database.
3. Document database attachment folder size to verify it is not growing too large for your version of SQL.
4. Notate which database is currently being used. Unused databases attached to SQL slow down the performance of ACT!
5. Verify if database backup is being made by Act Scheduler. Your database may not have been backed up by your server backup software!
6. Verify if database is being checked and repaired weekly by Act Scheduler. ACT! will run faster, take up less space, and errors can be corrected by running this.
7. Document path to backup zip file and size of backup to be sure it is in a location that your server backup software is finding.
8. Run manual Check, Repair and Reindex on ACT! database.
9. Perform other necessary diagnostics.
10. Document number of uncleared activities, which is the number one issue that slows down ACT!.
11. Document number of cleared activities to determine if old data needs to be removed.
12. Document data inconsistencies in primary fields such as state and email.
13. Document empty ID/Status field and create a dynamic group of those contacts. The ID/Status is one of the most important fields in ACT! and needs to be populated for successful use of ACT!.
14. Document empty Email field and create group of those contacts.
15. Scan database for duplicates based on Company, Contact and Phone; and Company, Contact and Address 1 and document those duplicates. A contact should be in the database only once!
16. Document how ACT! Update preference on the server is set to prevent users from accidentally updating their workstation.
17. If using remote databases, document the last time the users successfully synced.