Before you begin

IBM® recommends that you do the following:

• Keep the index data for any given version of a report in the database on disk at least until such time that 99 percent of the requests for the report have passed. As a rule of thumb, if there is any chance that someone in your organization will need to retrieve a version of a report, keep the index data in the database – don't allow it to be migrated.
• Expire data periodically, and migrate index data only when absolutely necessary.
• Select Multiple Loads per Database Table when you define the Database Organization within your application group definitions. With this selection, each time that you load a report into an application group, IBM Content Manager OnDemand inserts the index records into an existing database table. Index records for every report loaded into the application group are stored in the same database table. Content Manager OnDemand maintains the application group data so that, as far as a user querying the application group knows, they appear to reside in one database table. Content Manager OnDemand automatically segments the application group data when it grows beyond a certain size (unless you select Single table for all loads). Content Manager OnDemand maintains a segment table for each instance. The segment table provides faster query performance by limiting searches to a specific table of application group data, using a date value to construct the query. This method is the default, and should be used in most cases.