Question

A developer accidentally ran an UPDATE without a WHERE clause against a production Azure SQL Database at approximately 14:22 UTC, corrupting a critical table. The team discovered the issue at 15:10 UTC. The database is on the General Purpose tier with the default backup retention. Management wants the fastest recovery path that returns the data to its state just before the erroneous update while preserving the ability to compare against current data. What should you do?

Accepted Answer

Perform a point-in-time restore to a new database using a timestamp just before 14:22 UTC, then reconcile the affected table into the production database.

Answer

Restore the most recent long-term retention (LTR) weekly backup over the existing production database.

Answer

Configure active geo-replication and fail over to the secondary to recover the pre-update data.

Answer

Overwrite the existing production database with a point-in-time restore to 14:22 UTC.