Data Rescue
Recovery engines, one-shot repair scripts, and backup discipline for data you cannot lose. The craft of touching production data with a cap, a dry run, and an audit log.
14 posts · ~62 min total reading
-
Before you repair data, build the diagnostic
-
7 games became 14: making a bulk insert idempotent with an origin key
-
The One-Shot Data-Repair Script as a First-Class Artifact
-
Same Root Cause Is Not Same Fix: Verify the Data Shape, Not Just the Symptom
-
When a Workflow Gap Needs an Operator Tool: Preview, Policy, and an Audit Trail
-
When the Paywall Flow Is Broken, Build the Staff Tool, With Dry-Run, a Cap, and an Audit Row
-
The Auto-Approval Feature That Quietly Rewrote Curated Data
-
My backups had been dead for three weeks. I found out by accident.
-
A Migration Became the Audit I Had Never Run
-
The Fastest Legacy Hotfix Is Often a Diagnostic
-
1900-01-01 Is Not a Date: The Zero-Datetime That Corrupts Every Migration
-
A code-first schema audit: keeping a 1,477-line ASP file in sync with a 14,536-column DB
-
I Wrote a 1,477-Line Site-Recovery Engine in Classic ASP: Copy First, Remap IDs Second
-
Don't leave the recovery gun loaded: scrubbing prod constants at end of day