Welcome to the beta - and many thanks for your interest in testing SQLaudit.
Please direct any feedback to the SQLaudit Beta Forum - if you're reporting an issue, please include as much information as possible, including details on how to reproduce the problem, any error messages shown (or screenshots).
There's no documentation on how to use SQLaudit yet, but you should find it's fairly straightforward to use (if you don't, let me know!). Note that I've not included an option to apply the triggers automatically - you'll need to copy/paste the script into SSMS and run it, or save/load it and do likewise.
I look forward to hearing from you, and I hope your experience of SQLaudit is a good one.
Thanks again for all your efforts!
System requirements:
- Windows 2000 Service Pack 3; Windows 98; Windows 98 Second Edition; Windows ME; Windows Server 2003; Windows XP Service Pack 2.
- Microsoft .NET Framework 2.0 SP1.
Known issues/limitations:
- Values from VARCHAR and NVARCHAR columns are truncate to 8000 or 4000 characters respectively when audited.
- TEXT, NTEXT, IMAGE, TIMESTAMP, SQL_VARIANT, HIERARCHYID, and XML columns are not audited.
- Auditing information is stored in tables prefixed with SQLaudit_ - this will be configurable.
- Auditing information is stored in the same database as the audited tables.
- There's no user-interface (yet) for viewing audit logs - however, the auditing scripts create a view named dbo.SQLaudit_vw_Changes which contains all the pertinent information.
- The primary key on an audited table can have at most four columns - and the total column length for all columns in the primary key cannot exceed 900 bytes.
|
