One Keystroke, Three Years Gone – And How We Got It Back
At 2:17 p.m. on an ordinary Tuesday, a junior DBA ran DROP TABLE customers; in production. Three years of transaction history disappeared instantly. The daily backup was four days old. The VM snapshot was six months stale. The only surviving copy was a quarterly full backup archived 180 days earlier.
Human error never takes a day off. Dropped tables, missing WHERE clauses, and bad schema changes happen regularly and often go undetected for days.
SQL Server cannot restore a single table directly. The only supported method is to restore the entire database to a sandbox instance, then copy the needed objects back to production.
We restored that 180-day-old 2 TB quarterly backup overnight, extracted the lost table, and merged the historical data back the next morning. Six months of recent transactions were lost, but millions of dollars in older records were saved – all because one inexpensive archive backup still existed.
Daily and weekly backups protect you from small mistakes. Only long-term quarterly or yearly full backups protect you from the rare catastrophe that is months old. With modern cloud archive pricing, keeping them costs almost nothing compared to the risk.
Before the next accident happens, enable log backups, practice point-in-time restores, automate weekly sandbox restores, and schedule true long-term full backups.
More from Stedman Solutions:
Steve and the team at Stedman Solutions are here for all your SQL Server needs.
Contact us today for your free 30 minute consultation..
We are ready to help!