Parsing SQL Server transaction log file for practical solutions

Each SQL Server database has a transaction log that records all transactions and database changes made by each transaction. Transaction log files are intended for internal uses of the server and not be accessible to users.

This is not 'another session' about the SQL Server transaction log Architecture or how SQL Server uses the transaction log! This session is about how we can read and parse the contents of the transaction log files for practical solutions in real-case scenarios! In this session, we will go over questions that arise in forums from time to time and solutions that are based on thinking outside the box. We will utilize the information that is inaccessible in conventional ways and is intended for internal use, utilizing undocumented tools.

Case scenarios that we will investigate include parsing the log file and the backup files; finding the OS user which created a specific table; knowing who deleted data from a table; a solution for the error "Online index operations can only be performed in Enterprise edition of SQL Server" while running Transactional Replication from SQL Server Enterprise to SQL Server Standard; finding unused tables; restoring data manually from the transaction log file; and more...

This session is level 500

Ronen Ariely

Senior consultant and architect, data platform and application development.

Tel Aviv, Israel


Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.

Jump to top