What is a Database Automation?

Classic DBA tasks like taking backups, applying schema migrations, rotating credentials, and monitoring for slow queries used to require a human running commands at the right time. Automation turns each of those into a scheduled or triggered job: backups run on a fixed cadence with automated verification that the backup is actually restorable, migrations run through a versioned pipeline rather than a hand-typed SQL script, and alerting fires automatically when a query pattern degrades. The stakes here are unusually high compared to other automation categories, because a database automation mistake - a bad migration, an over-aggressive cleanup job - can cause irreversible data loss rather than just an inconvenience. This is why mature database automation treats destructive operations (drops, truncates, deletions) as requiring explicit human approval even when everything else is automated, and additive operations (new backups, new read replicas) as safe to run unattended. Good database automation also automates the boring-but-critical parts of compliance: proving a restore actually works, not just that a backup file exists.