82 IBM Content Manager OnDemand Guide
Three more tables might grow rapidly during the lifetime of a Content Manager OnDemand 
system: 
/SM590000The annotation table (ARSANN) grows in proportion to the volume of the annotations that 
are added to the documents. The system creates one row for every annotation. Therefore, 
every yellow sticker and every graphical annotation add one row to this table.
/SM590000The resource table (ARSRES) grows in proportion to the volume of AFP data that is 
archived and the resources’ (such as formdef, page segments, and overlays) frequency of 
change. 
/SM590000The load table (ARSLOAD) grows in proportion to the number of arsload jobs/tasks that 
are run. The Content Manager OnDemand system creates one row for each load job/task 
that is run. The load table (see Table 4-4) can grow to a multimillion row table during the 
lifetime of a Content Manager OnDemand system.
Table 4-4 shows the first four columns for the ARSLOAD table structure.
Table 4-4   ARSLOAD table structure
4.3  Relationship between tables when data is loaded
In this section, we present an example that shows the relationships between the Content 
Manager OnDemand tables when you are loading data to a Content Manager OnDemand 
system. This example is based on a check application that has four index fields that are 
defined as customer_name, account_nbr, check_nbr, and balance. A one-to-one relationship 
exists between the application group and the application. 
After the application group and the application are defined, the application group gets an 
application group identifier, agid, in the ARSAG table and an internal application group 
identifier, agid_name. Figure 4-2 on page 83 shows the data that is created in the ARSAG 
table; the agid is 5018, and the agid_name is HAA. 
Column 
name
Data type Size Index Description
agid integer 4 Y Application group identifier
pri_nid smallint 2 N Primary storage node identifier
sec_nid smallint 2 N Secondary storage node identifier
name varchar 11 Y Name of the load