The OnBase database can exist as a single filegroup (SQL Server) or tablespace (Oracle), or with multiple filegroups/tablespaces (DBSpaces). It is recommended that all production systems utilize DBSpaces, regardless of the initial estimation of database size. The existence of DBSpaces allows the database files to be spread across multiple hard drives, providing flexibility, scalability, and the ability to maximize disk performance.
Data in the OnBase database spaces fall into nine different logical storage categories:
|
Data Category |
Database Space |
|---|---|
|
Working Area, Log Tables, Medical Records Data |
DBSpace1 |
|
Document Data |
DBSpace2, DBSpace9 |
|
Keyword Data |
DBSpace3, DBSpace6 |
|
Document Indexes |
DBSpace2i, DBSpace9i |
|
Keyword Indexes |
DBSpace3i, DBSpace6i |
|
Reserved |
DBSpace4, DBSpace5 |
|
Folder Configuration, Data and Indexes |
DBSpace7 |
|
Configuration Data |
DBSpace8 |
|
Workflow Data, Batch Information, Configuration Data |
DBSpace10 |
The database space names are hard-coded and cannot be modified. If database spaces are not created, all objects will be placed into the primary filegroup (SQL Server) or default tablespace (Oracle) for hsi.