Database Maintenance program
|
Example: A client was unable to get into their database due to corruption. If maintenance was performed on a regular basis, existing corruption could have been identified in advance and addressed.
Due to the severity of the corruption, our only option was to restore the database from backup. Unfortunately, the most recent backup was 3 months old. The client ended up losing 3 months worth of data. If maintenance was performed on a regular basis, this could have been avoided by ensuring that backups were being performed on a routine basis.
|
Top 5 reasons to perform maintenance:
1. Ensure that backups are being performed.
2. Minimizes “Break/Fix” cost surprises.
3. Optimizes database performance.
4. Identifies potential issues before they occur.
5. Keeps you informed on what’s going on in your database.
Reasons to allow Stewart Technologies, Inc. to perform these items:
1. Assurance that maintenance is performed on a pre-determined basis.
2. Having your database reviewed by an expert who can identify issues.
3. Addressing issues before they become major problems.
4. Professional communication to IT and management, keeping parties “in the know”.
5. Peace of mind, allowing you to keep your focus on your business.
Maintenance can be performed on a weekly, bi-weekly or monthly schedule based on your needs. Items included in the maintenance program are bulleted below.
ACT! maintenance performed on server:
· Check and document free space on all drives on the server.
· Notate where database(s) is located.
· Check what ACT! version you are currently on.
· Make sure you are on current service pack & hotfix.
· Review attachment size(s).
· Notate which database(s) are currently being used.
· Make sure that backups are being made (ACT! scheduler). Document backup method. Make sure backups are not being saved under “Backup” folder.
· Back up ACT! Database(s).
· Document path to backup(s), size of backup(s).
· Do a test restore of the backup.
· Document size of database(s), number of contacts in database(s).
· Perform check, repair, reindex.
· Scan database(s) for duplicates.
· If duplicates exist, create a group called “Duplicates” and add contacts that are duplicates to that group.
· Copy serial numbers and users.
· Document users and their logins, active & inactive, ensuring there are at least 2 ACT! administrators.
· Make sure ACT! update preference is unchecked.
· Review Activities (see what is cleared and not cleared).
· Check antivirus software – make sure it is not scanning ACT! files.
· Check programs running (services.msc).
Sync maintenance performed: (if applicable)
· Check to make sure the sync service is on.
· Document sync method.
· Document sync server.
· Check to make sure all users are syncing.
· Document last time they synced.
Summary
· Summarize findings to client.
CLICK HERE IF YOU ARE INTERESTED
|
