The Foundation DBUtils application is used to create all OnBase data objects in their designated physical locations. This document refers to DBSpaces as the required physical filegroups (in a SQL database) or tablespaces (in an Oracle database) that the Foundation DBUtils application creates to store all the OnBase tables and indexes. Each DBSpace categorizes the specific data components and separates tables and indexes based on their specific function within OnBase. For example, all Keyword tables are created in DBSpace3 and DBSpace6. Having multiple DBSpaces provides the ability to balance I/O across spindles if needed. Having multiple DBSpaces can also reduce backup and restore times.
The tables are generally very small (the majority have fewer than five columns), with the largest tables (those containing 20-50 fields) composing less than 5% of the total number of tables in the database. The most prevalent data types are INT or BIGINT, CHAR, and DATETIME. Ten DBSpaces have been designated for table storage; the other four exist for index storage. The main document and logging tables are located in DBSpace1, DBSpace2, DBSpace3, DBSpace6, and DBSpace9. The index tables are DBSpace2i, DBSpace3i, DBSpace6i, and DBSpace9i. The majority of the growth and table/index access will occur in these physical storage groups. Therefore, these groups should receive close attention when considering performance optimization and sizing. For more information, see Database Sizing and Layout. Configuration tables and additional document information are located in the remaining five DBSpaces.
Non-clustered indexes exist on the majority of the tables. The larger transaction tables contain additional indexes (many of which are composite) that allow for increased performance when queries containing table joins are executed from OnBase. Primary keys exist only for tables specific to the WorkView module, and the majority of the tables contain a unique identifier column with an associated unique, non-clustered index.