The section on letting the database enforce the rules, not only the application, is a useful starting point. A NOT NULL, a foreign key, or a CHECK constraint will still apply when a new path writes to the same table. I also appreciated the habit of proving a backup actually restores, rather than only confirming that a backup job ran. The "where it does not fit" part is just as valuable as the praise. Knowing when to pick something else keeps this from being a one-tool answer.