The Costs of Azure SQL Database Backups
Updated April 26th 2016
This post is dated, and I decided to update it with information from Azure SQL Database: Built-in Backups vs Import/Export and from SQL Database FAQ.
Azure SQL Database billing is prorated
daily hourly. This means that if you create a database and delete it right away, you are be billed for the full day hour. Each hour is billed at the highest service tier + performance level that was applied during that hour.
I bring this up because the Azure SQL Database automatic backup feature
is was built on top of the import/export service. The export follows best practices in order to create a consistent point-in-time copy of your database. This copy is treated as a second database and is billed as such. Then the service exports this copy it to a bacpac file and places it in your Azure Storage.
Today the built-in backup feature is included in the hourly cost of each database. The following is a quick summary of its capabilities.
What are Azure SQL Database Built-in Backups?
Basic, standard, and premium databases are backed up automatically in Azure SQL Database. These backups are retained for 7 days, 14 days, and 35 days respectively. With these backups Azure SQL Database supports two restore capabilities.
- Point in Time Restore allows a database to be restored to any point in time, up to the millisecond, within a database’s retention period.
- Geo-Restore utilizes a database’s latest geo-redundant backup to recover a database. This means a database can be recovered in the event of a regional outage with the 1 hour old geo-redundant backup.
|Capability||Basic tier||Standard tier||Premium tier|
|Point In Time Restore||Any restore point within 7 days||Any restore point within 14 days||Any restore point within 35 days|
|Geo-Restore||ERT < 12h, RPO < 1h||ERT < 12h, RPO < 1h||ERT < 12h, RPO < 1h|
|Standard Geo-Replication||not included||ERT < 30s, RPO < 5s||ERT < 30s, RPO < 5s|
|Active Geo-Replication||not included||not included||ERT < 30s, RPO < 5s|