Although there is minimal maintenance required on the InterAction database, the physical database requires regular maintenance in order to maintain optimum performance. You must use the database utilities included with your database platform to make changes to the physical database.
When managing the physical database, you should use the following guidelines:
- Schedule regular database backups to be performed nightly if not several times a day.
- For SQL Server, back up the transaction log regularly. Generally, about four times a day is recommended.
- Do some performance testing on the servers.
- Perform regular server maintenance as recommended by your database system vendor. Maintenance tasks such as rebuilding the indexes help maintain good InterAction performance. See “Database Disaster Recovery” on page 290 for more suggestions about maintenance tasks.
- Dedicate a server for InterAction. The database processes rely heavily on CPU, memory, and bandwidth resources to support the user community.
- Do not share the server with other server applications or system services such as fax servers. These services generally rely heavily on CPU and bandwidth resources, thus significantly degrading InterAction performance.
- Do not share the server with other database applications such as document management systems.