Privacy-first · Data never leaves your server

Undo any SQL Server
mistake. Instantly.

rollback4sqlserver reads your transaction log and generates the exact inverse SQL to undo any INSERT, UPDATE, or DELETE — in seconds. No backup restore needed.

Open Dashboard → How it works
Generated Rollback Script — 3 events
-- ⚠ REVIEW CAREFULLY BEFORE EXECUTING
BEGIN TRANSACTION;
 
-- LSN 0000002C:0000029D DELETE → INSERT (undo)
INSERT INTO [dbo].[Orders]
  ([OrderID], [CustomerName], [Amount])
  VALUES (2, N'Bob', 275.50);
 
-- LSN 0000002C:00000297 UPDATE → UPDATE (undo)
UPDATE [dbo].[Orders]
  SET [Amount] = 150.00
  WHERE [OrderID] = 1;
 
-- COMMIT TRANSACTION; ← uncomment after review

The Problem

One bad UPDATE.
Thousands of corrupted rows.

SQL Server has no built-in undo button for committed transactions. Traditional recovery means restoring a full backup — hours of downtime. We fix that.

Features

Everything you need for log-based recovery.

Privacy-First Architecture

Agent runs locally on your Windows server. Browser connects to localhost:8182. Your transaction data never leaves your infrastructure.

Inverse SQL Engine

Automatically generates exact rollback SQL for every committed change: INSERT → DELETE, DELETE → INSERT, UPDATE → UPDATE with before-image values.

Live Log Monitoring

Polls fn_dblog every 5 seconds. New events appear in real time. Zero impact on SQL Server — pure SELECT, no DML/DDL.

Bulk Rollback Scripts

Select multiple events, click Generate. Get a complete BEGIN TRANSACTION script with all inverse operations in correct reverse-LSN order.

Zero Installation

Single .exe with embedded DuckDB. No SQL Server components, no .NET runtime, no service installation. Just run it.

Powerful Filtering

Filter by database, schema, table, operation type, time range, and full-text search. Point-in-time recovery for any window in your log history.

How it works

Up and running in 60 seconds.

Three steps from zero to full recovery capability.

1

Run the agent on your Windows server

Download logrecovery.exe and run it with your SQL Server credentials. Connects read-only — no changes made to your database.

C:\> .\logrecovery.exe serve --host ".\SQLEXPRESS" --user sa --pass *** --all-dbs --since 24h
2

Open the dashboard in your browser

Navigate to rollback4sqlserver.dbaops.io from any browser on the same machine. The UI connects directly to the local agent — your data stays local.

3

Select events → Generate Rollback Script

Filter events by table, time range, or operation. Select the rows to undo. Click Generate Rollback Script — review the SQL, then execute in SSMS or your preferred tool.

Architecture

Your data never leaves your server.

The cloud hosts only the UI shell — a static HTML page. All SQL Server access happens locally on your machine via the agent process.

── Data flow ──────────────────────────────────────────────────
Browser → rollback4sqlserver.dbaops.io (static HTML, Cloudflare CDN)
Browser → localhost:8182 (local agent, your machine)
Agent → SQL Server fn_dblog (read-only SELECT, no DDL/DML)
Agent → DuckDB (in-memory) (embedded, no external DB)
✓ SQL Server data never sent to the cloud

Ready to undo that mistake?

Free. Single exe. Works with SQL Server 2016 and above.

Open Dashboard →