Revert Database

Front 1

Unsupported conditions

Back 1

1. The database must currently have only one database snapshot, to which you plan to revert.
2. Any read-only or compressed filegroups exist in the database.
3. Any files are now offline but were online when the snapshot was created.

Front 2

Limitations

Back 2

Not intended for media recovery. Snapshot is an incomplete copy of the database files, so if database or database snapshot is corrupted, reverting is likely impossible or may not correct the problem.
Must use full recovery model.
Original Source database is overwritten by the reverted database, so any updates to the database since the snapshot's creation are lost.
The revert operation overwrites the old log file and rebuilds the log. Therefore back up log before reverting.
Reverting breaks teh log backup chain. Take a full database backup or file backup. Full db backup is recommended.
During a revert operation, both the snapshot and the source database are unavailable. The source db and snapshot are both marked "In restore" IF an error occurs during the revert operation, when the db starts up again, the revert operation will try to finish reverting.
The metadata of a reverted db is the same as the metadata at the time of the snapshot
Reverting drops all the full-text catelogs

Front 3

prerequisites

Back 3

Verify that the db has not become corrupted (if corrupted, restore it from backups)
Identify a recent snapshot that was created before the error.
Drop any other snapshots.