If you are a database administrator...

• Save yourself the laborious task of writing and debugging scripts to scan your SQL Server database tables and generate audit trail triggers.
• Avoid subtle mistakes made in home-grown audit trails when detecting changed values such as changing between a null and not null state.
• Help your organization comply with internal or regulatory audit trail requirements in a fraction of the time.
• Spot check problem areas in your databases so you can more easily track down and troubleshoot the origin of data corruption.

If you are a software developer...

• Eliminate the need to code and debug change-detection algorithms throughout your application wherever it manipulates data.
• Be assured of audit coverage; client-side coding can easily overlook fields or miss nonobvious data altering side-effects.
• Even if an audit trail is not a required feature of your application, use audit trails in the development of any database application to trace data changes made by complex functions; verify correctness and find unintentional side-effects faster and easier.

If you are a quality assurance specialist...

• Use audit trails in testing not only to make sure data was changed correctly, but to verify that no other data was changed unintentionally.
• Examining an audit trail for data changes (intentional and unintentional) is much faster and more accurate than scanning a SQL Profiler trace for data modification query statements.
• Adding or removing an audit trail is so effortless, auditing can be a standard element of your testing and could always be available even before you realize you need it.

If you are an ISV...

• Add audit trails to your SQL Server/MSDE-based software product by bundling OmniAudit and save yourself the development and testing effort.