Comment by jiggawatts
9 hours ago
Azure SQL Database did this too for a while until enough companies complained about losing their data and their backups with a single action.
9 hours ago
Azure SQL Database did this too for a while until enough companies complained about losing their data and their backups with a single action.
With the difference that best practices in Azure SQL have always been to store your own copies of backups and run the database in some HA/GEO-redundancy mode that blocks deletion.
Which sounds great, except that Azure SQL -- like many cloud services -- was carefully designed to be a tarpit into which you can import your data, but can't get your data back out.
For example, for at least a few years its "external" backups were simply the bacpac export function, which wasn't transactionally consistent and had all sorts of fun limits.