Craig Hatley, Director of Operations, Iatric Systems, Inc.
See more
Determine who changed data and when the change occurred. Read the transaction log to find out who created, changed or dropped a database object
Reverse inadvertent or malicious database changes that occurred even before the product was installed. Replay all valid SQL transactions on a different database
Read SQL Server database transaction logs to find out exactly when and how an accident occurred as well as details on who was involved
Identify users by their SQL or Windows login or host and application name
Recover from specific data loss/damage without relying on full database restores
Track permissions changes and trigger state
Isolate specific transactions by user, date, object, change type and more
Create end-user reports to document the changes in your environments
Schedule database audits unattended via the CLI