At a previous employer, we had a well-defined process when dropping databases for a client. It went something like this:
- Confirm in writing the databases on which servers/instances to be dropped
- Take a final full backup of databases
- Take databases offline
- Wait at least two weeks to make sure nothing breaks in the absence of this database
- Drop databases
This is a pretty good and safe method. If taking the database offline causes some unforeseen system to stop working, it can be very quickly brought back online in-place, instead of having to locate the backup and restore it. But it there’s just one problem…
Read on for that problem and its solution.