So I have a large database that we currently take snapshots of before deploying code, data, and schema changes. The problem I am trying to avoid is this. In case there is a need to revert back to
the original source database it will require two things. First you will need to remove the database from the availability group to get exclusive access. And secondly after reverting taking a full backup in order to rejoin the
AG. My question boils down to this is there a way to do this without involving taking backups which could take hours on a VLDB. So for large databases and the need to take snapshots and to revert might be buyer beware. Any other ideas or suggestions
are welcomed as to how to work with a VLDB and reverting a snapshot?
↧