The Gnosis Auditable Database has the ability to view on-line data as well as historical data concurrently for users independently of one another. Thus one user may be examining historical transactions or running reports on historical data whereas most other users will be working with and making changes to current (on-line) data. |
 |
The capability to view different data sets is achived by looking at the database through sql-server-views that can be easily switched from current (on-line) data to historical data. |
| Gnosis tables utilise the Microsoft Sql Server 2005 partitioned tables. The above diagram illustrates a partitioned table broken into two historical Archives, Current and Transaction datasets. Thus a user who is viewing current on-line data will not attempt to access any historical data, whereas a user who is accessing an historical archive will not access data outside of the historical archive such as current data or data from a completely different historical period. |
Gnosis Temporal Index |
The Gnosis Temporal Index exists within an Archive, and enables a query to the Archive to retrieve far less rows than would otherwise occur. |
 |
The Temporal Index allows the query at the given historical date and time to need only look at a subset of the data stored in the Archive. The diagram illustrates an Archive that has 3 levels and is split into 3, 9 and 27 files per level. The red indicates where the queries are looking for data. |
Transactional Replication Subscriber |
Typically the Gnosis Auditable database is implemented as a Transaction replication subscriber. Which means that there is minimal impact to the performance of the on-line system in implementing an Auditable Database, and processing overheads in accessing auditable data are separated from on-line processing requirements. |
| |
