OmniAudit automatically and transparently tracks changes to data in any column of any table in your Microsoft SQL Server databases. Simply select the tables and columns you want to audit, and OmniAudit does everything for you.
OmniAudit captures changes regardless of the application used to change the data: a commercial software package, an in-house application, or even the native tools provided with SQL Server such as Query Analyzer.
OmniAudit catches it all and records what data was changed and who changed it. OmniAudit not only captures before and after values for each changed column, but also identifies: the user, date and time, the workstation used, and the application used to make the change.
You decide which tables and columns to audit; OmniAudit automatically generates triggers to maintain an audit trail of all inserts, updates, and deletes made to that data. OmniAudit is a completely server-side solution which requires no modifications to any client software.
Data auditing can be valuable to an IT organization in a number of ways: * Database administrators can more easily troubleshoot and track down the origin of data corruption. Organizations with internal or regulatory requirements for following the history of data can do so easily, even if their software doesn't already handle this requirement.
Software developers can more easily develop and debug applications by tracing how data gets changed by any particular function of the software. Find unintentional side-effects faster and easier.
Quality Assurance functions can validate data altering features more quickly and with greater accuracy. Using OmniAudit Log Viewer, you can quickly and easily sift through the compiled audit log history in a number of ways. Filter audit log data on date/time, table/column, user, workstation, any of the key variables tracked by OmniAudit. Audit log data can be exported to standard file formats including text, Excel and XML.
Here are some key features of "OmniAudit":
Point-And-Click Setup; Be Auditing in Minutes:
· Check off the tables and fields you want to audit, select a few options, click a button and OmniAudit creates the audit trail tables and triggers for you.
Analyze Audit Trail Data Without Knowing SQL:
· The included OmniAudit Log Viewer tool lets you easily zero in on audit data by table, field, user, date, workstation, or application. Save the results to an Excel worksheet, HTML or XML document, or plain text.
Accessible Audit Trail Data:
· Audit trail data is stored in SQL Server tables and can be accessed using normal SQL Server query tools (provided you have given the user security access).
Nonintrusive:
· Auditing is performed on the server and requires no modifications to client software.
Capture Reference Data, Not Just Changed Data:
· When an audited value changes, you can have additional values from that row added to the audit trail...whether they changed or not. For example, you can have EmployeeNum written in the audit trail whenever ANY data in the Employee row changes.
Automatically Purge Audit Trail Data:
· Depending on your auditing requirements, you may only be interested in retaining recent audit history. You can configure OmniAudit to automatically purge audit trail history after a given number of days, weeks, or months have passed.
Requirements:
· Microsoft Data Access Components (MDAC) 2.6 or higher
Limitations:
· 30 days trial
· nag screen
What's New in This Release: [ read full changelog ]
· Added new audit trigger option "Blank is Equivalent to Null". When this option is enabled, zero-length (empty) character values are considered null for all purposes of auditing. See the help under Trigger Options for more information.
· Added a preferences dialog to permit customizing the database query timeout duration; default is 5 minutes.
· Fixed an error when connecting to a database with a user that is not a database owner: "Field 'GroupName' not found".
· Fixed an issue where in a specific circumstance trial version auditing in a database may not be updated using registered software.
· Fixed some documentation mistakes.
Find us on Google+
