SQL Anywhere Studio Security Guide
Keeping Your Data Secure
Auditing is a way of keeping track of the activity performed on a database. The record of activities stays in the transaction log. By turning on auditing, the DBA increases the amount of data saved in the transaction log to include the following:
All login attempts (successful and failed), including the terminal ID.
Accurate timestamps of all events (to a resolution of milliseconds)
All permissions checks (successful and failed), including the object on which the permission was checked (if applicable)
All actions that require DBA authority.
Each database has an associated transaction log file. The transaction log is used for database recovery. It is a record of transactions executed against a database.
For information about the transaction log, see The transaction log.
The transaction log stores all executed data definition statements, and the user ID that executed them. It also stores all updates, deletes, and inserts and which user executed those statements. However, this is insufficient for some auditing purposes. By default, the transaction log does not contain the time of the event, just the order in which events occurred. It also contains neither failed events, nor select statements.
Turning on auditing
Retrieving audit information
Adding audit comments
An auditing example
Auditing actions outside the database server