OmniAudit > Version History
Version History
OmniAudit
This shows you how often OmniAudit was updated with us over the past few months. Whenever available, we also include additional information for each update (new features, changes etc.).
version 1.12 - posted on Jan 05, 2009
- No further details available
version 1.11.2 - posted on Mar 27, 2008
- No further details available
version 1.11 - posted on Jan 14, 2008
- No further details available
version 1.10.1 - posted on Oct 24, 2007
- No further details available
version 1.10 - posted on Oct 03, 2007
- No further details available
version 1.9 - posted on Sep 17, 2007
- No further details available
version 1.8.2 - posted on Jun 13, 2006
- No further details available
version 1.8 - posted on Jun 01, 2006
- No further details available
version 1.7.3 - posted on Feb 23, 2006
- No further details available
version 1.7.2 - posted on Dec 20, 2005
- No further details available
version 1.7.1 - posted on Nov 30, 2005
- No further details available
version 1.7.0 - posted on Nov 09, 2005
- No further details available
version 1.6.9 - posted on Jul 28, 2005
- No further details available
version 1.6.8 - posted on Jul 05, 2005
- No further details available
version 1.6.7 - posted on Mar 30, 2005
- No further details available
version 1.6.6 - posted on Feb 22, 2005
- No further details available
version 1.6.5 - posted on Feb 09, 2005
- No further details available
version 1.6.4 - posted on Jan 25, 2005
- No further details available
version 1.6.3 - posted on Dec 16, 2004
- No further details available
version 1.6.2 - posted on Sep 13, 2004
- No further details available
version 1.6.1 - posted on Jun 02, 2004
- No further details available
version 1.6 - posted on Apr 30, 2004
- No further details available
version 1.59 - posted on Aug 01, 2003
- No further details available
version 1.57 - posted on Mar 18, 2003
- FIX: (OmniAudit Manager) Triggers produced an error: `Cannot insert null value into AuditLogDetail.RowKey` when a value in the unique key of the table as well as another non-key value in the same row are changed in the same transaction.
FIX: (OmniAudit Manager) When generating triggers across different table owners using the `All Owners` selection, would always get an error `No tables have been selected for auditing`.
FIX: (OmniAudit Manager) Getting errors `SQL Server does not exist` at the build trigger point when a port number is used to identify the server. Also happens when the SQL Server has been improperly renamed in the past and @@servername does not reflect the correct name of the server. Both issues are now resolved. Note: the 1.5.5 fix for @@servername dealt with the case when @@servername equaled null
this fix deals with the fact that @@servername is non-null, but different than the actual servername.
NEW: (OmniAudit Log Viewer) Added `preferences` dialog under the File menu. Preferences lets the user set the query timeout value.
version 1.56 - posted on Jan 17, 2003
- FIX: (Audit Manager) In databases with a large number of tables, regardless of how many tables were being audited, the `Build Triggers` process was taking a considerably long time to complete. The time to build triggers has been reduced substantially..
