Advantages of Gnosis Transactions
Please explain some of the advantages of Gnosis Transactions ?
Gnosis Transactions enable the system workflow to match very closely the business and customer workflow. Gnosis Transactions are work-in-progress and they can be stopped part way through and then completed at a later time, or they can be transferred from one user to another. Thus Gnosis Transactions will facilitate better and more efficient business processes, help improve the workflow of systems that serve customers and enable complex business to business transactions to be developed.
|
Combined Auditable Database and Gnosis Transactions
Can I create a system that is both an Auditable Database and performs Gnosis Transactions ?
Yes, you may combine Database Auditabilty and Gnosis Transactions, you may develop systems that utilise each individually or neither (using the Gnosis Business Rule Manager).
|
Can an Auditable Database be created for any database schema?
Yes, this is mostly correct. An auditable database is generated from its schema definition, which is stored in the Gnosis Business Rule Manager. A database schema can become and Auditable Database so long as it conforms to the schema integrity rules (ie. checked successfully) of the Gnosis Business Rule Manager.
|
What are the steps to migrate an existing database to a Gnosis database?
In broad terms the steps are:
- Migrate the schema using the Gnosis Business Rule Manager, which requires a source SQL database (schema) to be created on the same server as the Gnosis Database.
- Check and Generate the Gnosis database.
- Copy data from the SQL source database using sql statements. Or migrate data from the source database via data transfer mechanisms.
- For an Auditable Database, define and start an Audit Archive.
|
What are the greatest risks associated with migrating to an Auditable Database ?
We believe the greatest risks are associated with application migration and performance, here is a list of considerations...
- Be aware of existing instead of triggers on the on-line system.
- Applications that use SQL statements directly rather than use stored procedures present greater risk in migration.
- Ensure all applications and reports are tested thoroughly.on the Auditable database.
- An Auditable Database will require greater SQL Server processing power.
- Consider the number of Transactions you expect to be auditing and define Audit Archives accordingly.
|
License and Payment Considerations
How do I increase the License Size of my Gnosis Database ?
Please start the Gnosis Business Rule Manager application and go to the database you wish to increase in size and display the License tab. Change the Licensed database Size (and any other attributes that you require ) and click the Request License hyperlink, this will automatically create an email for you to send to Gnosis requesting the license Key upgrade. Please beware, Gnosis will likely require payment for this license upgrade before the license key is provided to you.
How do I pay for a Gnosis License when I am in another country?
Payments to Gnosis can be made by using PayPal, please request a licence key and we will reply with details of how to make payment to us.
|
Please sumarise your thinking regarding the design of a Gnosis Auditable database related to its performance?
The Gnosis Auditable database is typically envisaged to be setup in a Publisher Subscriber configuration. Where the existing online system becomes the Publisher and the Auditable database is the Subscriber to a transactional replication publication. Such a cofiguration causes the minimum impact to the on-line database, and allows for the audit data to be stored separate to its on-line counterpart.
|
Typically should all Tables of a database become Auditable ?
No. Some tables are already designed as auditable, and should not be managed by Gnosis. These tables usually allow only inserts and do not allow updates or deletes. Tables that have very high transaction throughput are often candidates for exclusion as are Tables that contain logs of user actions.
For example in a banking environment, auditability is highly applicabile to any data that is managed by bank users from banking applications or from customers via web interfaces. Typically this data contains customer details (name, address, etc), account details (such as auto payments) and banking business rules (such as interest rates, charges etc). Transaction detail data (such as credit or debit amounts) and automated data (such as downloaded exchange rates) would or may not require auditability.
|
Using Gnosis Applications
Must I use the Gnosis Work Manager to manage Gnosis Transactions ?
No, you can write your own equivalent application or incorporate transaction stored procedure calls into the user application. Gnosis Transactions are managed by calling a stored procedure interface, that can be called from any Web and/or Windows applications. The Gnosis Work Manager is in-part a demonstration of the capabilities of Gnosis Transactions - and an interface that could be used to manage them, it is not mandatory for running Gnosis Transactions.
Must I use the Gnosis Work Manager to manage Audit History ?
No, the same rasons apply. The Gnosis Work Manager offers an interface for managing and investigating historical transactions, however, we precieve far more powerful interfaces will be developed for specific user systems/applications. Again managing audit history is performed via the stored procedure and sql interface.
Must I use the Gnosis Business Rule Manager to manage Gnosis Databases?
The answer ot this question is typically Yes, however, you can script stored procedure and sql calls that manage the definition of a database. When you run the Evaluation setup program, the scripts define the database using stored procedure and sql statements. So the Business Rule Manager application is not needed if you have scripts..., however, the Gnosis Business Rule Manager is still applicable for examining the database definition after running scripts.
|
When I set an Auditable database to be viewed as at an historical date and time do I affect other on-line users ?
No, you will be viewing the Audit data, while they will be viewing the current (on-line) data. When you set your view to an historical point in time only your view is changed, all other users remain unchanged. The same principle applies to Gnosis Transactions.
|
| |
