The Gnosis Transaction Manager is designed specifically for Microsoft SQL Server™ and incorporates the following performance features.

Powerful Performance Architecture

The Gnosis Transaction architecture incorporates a breakthrough processing mechanism that offloads merge and rollback processing to a background task. This means that a merge or rollback is virtually instantaneous for any number of rows to any number of tables. With the ability to perform background processing over night or at low utilisation periods, the Gnosis architecture enables a more even computer loading curve, which means better utilisation of the processing resource.

The diagram shows the commit process broken into the check and merge steps, where the merge is virtually instantaneous, and is replaced by background processing, which can be configured to run continuously or at low utilisation periods. To Commit a Gnosis Transaction is checked (with result successful) before it can be merged into the Committed data set. In special circumstances the database owner may elect to commit a transaction without checking.

Background Processing.

The are three main tasks that are performed by Gnosis Background Processing.

Manage Permanent Temporary Tables

A Gnosis database uses permanent temporary tables to store calculations in progress. The temporary data is stored in sets of permanent temporary tables, and usage cycles between each set over designated periods of time. Background Processing manages these sets of permanent temporary tables.

Transaction Processing

The task of Transaction Processing is the process that is responsible for optimising data stored for Gnosis Transactions. This process merges the rows of committed Gnosis Transactions and discards rows of rolled-back Gnosis Transactions. This process can be executed as part of background processing or can be run at low usage periods such as overnight or weekend.

Build Temporal Index

Where the database is Auditable, a process is required to build the Temporal Index that enables access to historical data. Similarly, this process can be executed as part of background processing or can be run at low usage periods such as overnight or weekend.

Optimised Transaction Check Processing

The Gnosis Transaction Manager uses very powerful optimisation techniques for its business rule check processing. All generated stored procedures include table index hints, join hints and table access order hints. In addition check processing scales from one row to many very powerfully, as the cost of increment of checking multiple rows from the same SQL query is only fractionally more expensive.

Replication

The Gnosis Transaction architecture is compatible with SQL Server transactional and merge replication technologies. The Gnosis architecture does not utilise table triggers, which is works well with SQL Server merge replication technology (which utilises table triggers).

A large Gnosis Transaction, which contains thousands of row changes for example, committed at one site will within a very short time be visible at the central site and other remote sites too, as the row changes will very likely have been merged at an earlier time.