Andy Brownsword hits upon an underrated feature in SQL Server:
Deploying database changes are relatively easy. Where things get complicated is the rollback. Sure, it’s easy to script out and revert a procedure to a previous version, but what about destructive changes?
In this post we’ll look at how we can use Database Snapshots to remove some of the headache that comes with rolling back changes.
Read on to learn more. The most exciting thing I did with database snapshots was to create a simple app for my developers to take a snapshot (without needing to know the T-SQL behind it), make whatever changes they needed to, and then roll back or roll forward the changes.