ApexSQL Log
A SQL transaction log reader for forensic auditing
and rollback of malicious or inadvertent changes
This knowledge base article covers the various scenarios when you might benefit from reading the SQL Server transaction log with ApexSQL Log including auditing changes on a database schema or data, troubleshooting security issues, recovering data that was inadvertently updated or deleted, and more 
View deleted and damaged data. Reverse inadvertent or malicious database changes. Replay all transactions on a different database
View transactions in custom high performance grid with advanced instant filtering options and operate with more than 100 million operations at once
Track permissions changes and trigger states
Recover from a specific data loss/damage without relying on full database restores
Isolate specific SQL Server transactions by user, date, object, change type, and more
View the complete history of individual row changes over time
Group and sort transaction information to shape the view of transaction activity
Schedule unattended database audits via the CLI
Locate transactions by utilizing advanced grid search algorithms – regular expressions, transaction details and row history search
View BLOB fields (varbinary(MAX), varchar(MAX), nvarchar(MAX)…) in human-comprehensible form
Read the SQL Server transaction log to determine who changed what and when the change occurred, even before the product was installed
