In SQL Server databases, changes to the data in iBase entity and link records can be recorded.
- Entering and editing records
- Deleting records (including soft-deleted records)
- Batch editing
- Merging entities
- Assigning icons
- Importing data, including bulk import
- Editing code lists
- Record Added
- Record Modified
- Record Deleted (not including soft-deleted records)
- Code List Modified
- Bulk Import
Audited field types
Aside from data associated with calculated fields (that is not directly stored, but depend on values held in other fields) all field types can be audited. In the audit log, all data is converted to text apart from Document and Picture fields which are stored in their original format. You can view this historical data in Audit Viewer or in iBase itself when showing a record or link, unless permission to do so is denied.
What is recorded
- Original value
- iBase user who made a change
- Date and time the change was made
- Machine name of the editing user
- OS user name (name of the Windows user)
- Reason for the change
- SCC – needed to ensure that the user only sees the data they should if SCC values are altered during records history
- Location of user – from iBase user location
- Reason for the update (optional)
- Whether the update was made using an i2 product
- Data in the extra field (if this feature is used)
- The name of the account used to connect to SQL Server
Setting up audit history
To enable and set up audit history, in the iBase Designer Database Properties, turn on Audit History. An Audit History action is added to the audit log to record when, and who, enabled this feature.
- In iBase Designer, select System Commands Access Control>Reason For Action and turn on or off Data Auditing.
- In iBase Designer in the System Commands Access Control dialog, display the Access Denied page and turn on or off the View History check box.
You can also configure audit history to disable the guest account and replace it with an existing SQL Server login for audit history logging. For further details, see Changing account used to log audit history.
Maintaining auditing stored procedures
When a user logs into a database with Audit History turned on, checks are made on the SQL Server database and, if any problem is detected with auditing, the user is denied access to the database. To fix the problem, reopen the database in iBase Designer.