1,126
edits
Difference between revisions of "Content Manager OnDemand Database Tables"
Jump to navigation
Jump to search
Content Manager OnDemand Database Tables (view source)
Revision as of 20:21, 30 May 2016
, 20:21, 30 May 2016First Draft of ARSAG table information.
m (Jderrick moved page Deep-dive into ARS* tables to Content Manager OnDemand Database Tables: Sierra Echo Oscar) |
(First Draft of ARSAG table information.) |
||
| Line 1: | Line 1: | ||
{{TOCright}} | |||
= CMOD Database Tables = | |||
This article is a reference of the contents of database tables inside Content Manager OnDemand. | |||
== arsag - Application Group Table == | |||
This table contains all of the configuration data for Application Group Configuration in Content Manager OnDemand. | |||
{| class="wikitable" | |||
!Field!!Sample Values!!Type!!Description | |||
|- | |||
|NAME||System Log, AccountsPayable||String||Name of the Application Group. No special characters allowed. | |||
|- | |||
|DESCRIPTION||System Log, Accounts Payable||String||Description of the Application Group. | |||
|- | |||
|AGID||5001,5938,6938||Integer||Unique Numeric Identifier for Application Group. Used as a relation to ARSAGFLD, ARSAG2FLD, etc. | |||
|- | |||
|AGID_NAME||SL,HGA,IBA||String||Three-character unique Alpha identifier for Application Group. Used in database ("Segment") names, as a filespace name in TSM, and in the cache filesystem. | |||
|- | |||
|DB_SEG||1,2,3,1000||Integer||Used as a counter for the next database segment (table) number. | |||
|- | |||
|ANN_TYPE||?||?||Determines the Annotation Type for an Application Group. | |||
|- | |||
|DB_EXP_DATE||90,365,2557||Integer||Number of days to retain the documents loaded into this Application Group for. This field stores the Life of Data and Indexes value from the Administrative Client. | |||
|- | |||
|DB_MGRT_DATE||365,720,2557||Integer||Duration after which the database segement (aka table) is migrated to secondary storage. Rarely | |||
used. | |||
|- | |||
|SM_CACHE_DOC||90,366,720||Integer||The period for which data should be cached after being loaded. | |||
|- | |||
|RESGRP||1,2,3,40,30000||Integer||Used as a counter for the next Resource Group number. | |||
|- | |||
|LOAD_ID||1,359,497295||Integer||Used as a counter for the next LoadID number. | |||
|- | |||
|LOG||?||?||? | |||
|- | |||
|LOAD_ID_SUFFIX||FAA, GAA, HAA||String||Incremented for every 1 million LOAD_ID values. Incremented left-to-right from F to Z, A to Z, then A to Z until exhausted -- allowing for over 13.5 trillion loads in total. | |||
|- | |||
|MGRT_CACHE_DATE||30,45,90, 180||Integer||Number of days after loading when the documents are migrated to secondary storage. | |||
|- | |||
|REIMPORT_EXP_DATE||30,90,180||Integer||Number of days after which a re-imported database table is expired. | |||
|- | |||
|SID||1,80,88,837||Integer||The Storage Set ID Number. A unique integer is defined for each new Storage Set defined in the Administrative Client. | |||
|- | |||
|EXPIRE_TYPE | |||
|- | |||
|SEG_ROWS | |||
|- | |||
|SEG_ID | |||
|- | |||
|OBJ_SIZE | |||
|- | |||
|TYPE | |||
|- | |||
|UPD_USERID | |||
|- | |||
|UPD_DATE | |||
|- | |||
|LAST_DOC_DATE | |||
|- | |||
|MIGR_SRVR_STR | |||
|- | |||
|SM_CACHE_DELTA | |||
|- | |||
|DATABASE_NAME | |||
|- | |||
|SM_CACHE_RES | |||
|- | |||
|FTI_SERVER | |||
|- | |||
|UPD_DT | |||
|- | |||
|LAST_DOC_DT | |||
|- | |||
|LAST_LOAD_DT | |||
|- | |||
|LAST_QUERY_DT | |||
|- | |||
|LAST_RETR_DT | |||
|} | |||
== arsagfld - Application Group Fields Table == | == arsagfld - Application Group Fields Table == | ||