Database Administration
The FootPrints database design is optimized to work with the most popular relational databases for efficient and fast performance. This chapter covers the following topics:
- System Architecture—The general architecture of FootPrints.
- Database Design—Design of the FootPrints database, including table structure and connection types.
- Services—FootPrints services for connecting to the database.
- Database Maintenance—Purging and archiving Workspace data
- Backups and Disaster Recovery—Information about backing upFootPrints and creating a disaster recovery plan.
- Upgrades—About upgrades to FootPrints.
- Performance—Guidelines and troubleshooting system performance.
- Field-Limit-Specifications—Rules regarding the number of Workspace fields allowed based on database used.
- Security—About security in FootPrints.
Restrictions
With respect to limits for the number of fields in an individual workspace, there is very little danger of exceeding the limits of most databases. Nevertheless, administrators should be aware that when the number of fields in an individual workspace grow into the hundreds, performance may begin to degrade or data may be truncated.
There are two ways in which field proliferation might become a problem. One is through using field dependencies and the other is by using field-level permissions to combine multiple workspaces into a single workspace. Administrators should not in any way avoid using these features. They are mentioned here only because of the slim chance that they could cause a problem through field proliferation.