Database. An Auditable Database may be configured as

1. A Combined on-line and auditable database
2. A Publisher/Subscriber database pair where the Publisher is the on-line database and the Subscriber is the database containing audit data.

Archives. An Archive is a logical structure that defines how historical data is aggregated (or indexed) over a given number of transactions.. An Archive may be Active; indicating it is currently being used to define historical data structures, Historic; indicating it is for historical data structures, Validated, indicating the archive is fully defined and ready to become an Active Archive, and Not Validated; indicating the Archive definition is under construction and about to be validated.

Archive Levels. An archive is comprised of levels, which define the amount of aggregation that is used and the number of files that data is split over, for the Temporal Index. Each Archive has a Transaction capacity - for example an archive of 3 levels of aggregation of 8, 64, 1024 will have a transaction capacity of 524,288 transactions. This could be split over 1 file for each level or more than one file for the greater Archive levels.

File Groups. A Gnosis-File Group contains a set of information that defines where table data is placed. For an Auditable Database, a Gnosis-File Group defines where to physically store audit data in the File Group Archive..

File Group Archive. The Archive defines how historical data is structured for a designated number of Transactions, and the intersection of File Group and Archive (File Group Archive) has file path and file size attributes. These attributes are used to create SQL-Files and SQL-Filegroups for the File Group Archive and Level.

SQL-Filegroups are comprised of SQL-Files which require a path, file name and initial file size to be defined. The File Group Archive object stores data that is used to compose the file path, name and initial size of the SQL-File. The file name is derived from a File Prefix that is defined in the File Group Archive and a suffix that is derived on the Archive Level and the File Sequence Number.

Tables. Each Gnosis-table is placed on a Gnosis-File Group and has a field labelled Create Audit History which may be set when the Database is defined as an Auditable Database. We recommend all Gnosis-tables be set to Create Audit History unless the table performs only insert operations.

For more details on these topics please goto Gnosis Business Rule Manager or refer to the Gnosis Business Rule Manager Help, available from the Evaluation Version download.