Rockwell Automation Emonitor with a Gupta Single-User Database - Manual (Page 37)

4 • D ATABASE MAINTENANCE
33
•
•
•
• •
7. In the Input Window (top pane), type the following, including the semicolon:
check database;
8. Press Shift+F2 to execute the command. If the check is successful, SQLTalk displays
the message:
DATABASE CHECKED
If any other message appears, your database may be corrupt. Contact Customer
Support immediately for assistance. Repeat these steps for the Econfig database.
9. Type the following in the Input window (top pane), including the semicolon:
Update statistics on database;
10. Press Shift+F2 to execute the command. After SQLTalk executes the command, it
displays a message similar to this one depending on the number of rows in your
database:
STATISTICS UPDATED ON 13,443 ROWS
11. Repeat this command on the Econfig database. After the Update Statistics command is
finished, select File > Exit to exit SQLTalk.
12. Shut down the SQLBase engine (locally for single-user systems and at the server for
multi-user systems).
13. Back up the database subdirectories with your own backup software, or copy the
subdirectories to a network drive that is backed up. After backing up the database
directories, simply restart Emonitor (on single-user installations). For multi-user
installations, you must restart the database engine software before launching
Emonitor.
14. Remember to rotate the storage media (tapes or disks) in order to ensure that you have
at least one good previous backup set aside. This will help prevent the accidental
overwriting of the previous good backup with a bad one. A recommended back up
strategy would be to create separate tapes or disks that are used for annual, quarterly,
monthly and weekly backups.
Using the correct storage media for your data
To help prevent database corruption, do not run your database from removable storage
media such as Zip, JAZZ, Bernoulli, SyQuest, or SuperDISK drives. These removable
storage devices are excellent for backing up or copying databases, but are not suited to the
constant I/O requirements of the database engine.