A bug bear of mine for a long time has been the best practice of always having SQL server in full logging mode, with highly regular log backups. It's great for

A bug bear of mine for a long time has been the best practice of always having SQL server in full logging mode, with highly regular log backups. It's great for important production services. In practise I run test databases I could rebuild from scripts. Archive databases that never see a write. Databases that load and drop automatically from other sources. Every single time someone looks at these, there's a someone panicking about best practise. Something about this particular issue just makes critical thought non existent.