An analyst accidentally ran a bad UPDATE on a permanent table eight hours ago. The table has the default Time Travel retention and no clone or backup exists. The analyst wants to recover the pre-update values with the least effort. What should they do?
- AOpen a support case to retrieve the previous values from Fail-safe, because Fail-safe is the standard self-service mechanism for reverting a recent erroneous update on a permanent table
- BQuery the table using Time Travel with AT or BEFORE to read its state from just before the bad update, then restore those rows, since the change is within the retention window Correct
- CRun UNDROP TABLE on the affected table, which rolls the table back to the version that existed before the most recent update statement was committed against it
- DIncrease DATA_RETENTION_TIME_IN_DAYS on the table now, which retroactively extends the window backwards and recreates the pre-update version so it can be queried again
Why A is wrong: Fail-safe is tempting as a recovery tool, but it is a Snowflake-managed last resort accessed only via support, not a self-service way to undo a recent change still in Time Travel.
Why B is correct: Default retention is one day, so an eight-hour-old change sits inside the Time Travel window and AT or BEFORE returns the prior version for a direct restore.
Why C is wrong: UNDROP only restores a dropped object; the table was updated, not dropped, so UNDROP does nothing here and cannot revert an UPDATE statement.
Why D is wrong: Raising retention only affects history kept from now on; it cannot recreate a version that the original window already covers or restore data retroactively.