Getting Started — Log Reader

First successful read: connect to a FULL recovery database → choose Online log (or a .trn) → set a narrow time filter → open Log Entries → pick one INSERT/UPDATE/DELETE → generate a row-level undo script and review it offline first.

Getting Started

  1. Connect to SQL Server — Click the Connect button in the toolbar. Enter your server name and choose an authentication method (Windows Auth, SQL Auth, or Azure Entra ID). Click Connect.
  2. Select a database — After connecting, choose your target database from the Database dropdown. The dropdown lists all databases you have access to.
  3. Choose a time window — Use the Duration dropdown (Last 1 Hour, Last 2 Hours, etc.) to limit which log entries are shown, or switch to Date Range mode and enter specific From/To times.
  4. Read the log — Click the blue Read Log button. The status bar at the bottom shows reading progress. When complete, the Log Entries grid is populated with the most recent entries at the top.
  5. Explore the tabs — Switch between Log Entries, Transactions, Recovery, Analysis (Summary / Timeline / Row History), and Monitor to analyze the data from different angles.

Tip: The Exclude system txns checkbox (enabled by default) hides internal SQL Server background activity so you only see user-generated changes. Uncheck it and re-run Read Log to include system transactions.


Connection & Authentication

Use Connect / Change Server in the title bar to open the connection dialog. Supported authentication modes:

ModeWhen to use
Windows AuthenticationDefault for domain-joined workstations; uses your Windows identity.
SQL Server AuthenticationSQL login + password.
Azure Entra ID — PasswordEntra user with password (Azure SQL / MI).
Azure Entra ID — MFA InteractiveInteractive browser/MFA sign-in for Entra accounts that require MFA.

After connecting, pick a database from the dropdown (refresh with ↻). You can reconnect at any time without restarting the app.


Log Sources

SourceHow to selectWhat you see
Online Database Connect to a server and select a database. Leave the or File: field empty. All log records still in the active transaction log. How far back this goes depends on your recovery model and log backup frequency.
Log File (.ldf) Click Browse… and select a .ldf or .ndf file. All records in the detached log file. Requires sysadmin. The file path must be readable by the SQL Server service account.
Backup File (.bak / .trn) Click Browse… and select a .bak or .trn file. Transaction log records embedded in the backup. Useful for investigating what happened in a specific backup window.

Licensing

Log Reader uses the shared DBLense license store on your machine. From About you can:

  • Start a 14-day trial (one trial per machine)
  • Activate a license key online, or offline when the license server is unreachable
  • See edition, expiration, and trial status in the title-bar badge

Purchase and manage keys from the pricing page after signing in to your DBLense account.