Content Manager OnDemand database storage

When you load a report into the system, Content Manager OnDemand extracts index data from the report and stores it in an application group table in the database.

For reports that contain logical items, such as statements and policies, Content Manager OnDemand can create one database row for every item found in the report. For reports that contain sorted transaction data, Content Manager OnDemand can creates one database row for every indexed group of pages (by default, 100 pages in a group).

A database row contains a fixed amount of information that Content Manager OnDemand uses to maintain reports (approximately 40 bytes) and any additional index and filter fields that you define for the application group. Index fields, which allow users to locate documents quickly, require significantly more disk storage space than filter fields. (Index fields also require more time to load into Content Manager OnDemand.)

There are four major factors that determine the amount of disk space required for the Content Manager OnDemand database:
  • The number of index and filter fields
  • The size of the index and filter fields
  • The number of indexed items per month
  • The number of months that Content Manager OnDemand maintains the index data in the database
See the administrator online help for a list of the types of index fields supported by Content Manager OnDemand and the number of bytes required to store a value in each type of index field.