Most database restores finish in less than 12 hours.įor a single subscription, you have the following limitations on the number of concurrent restore requests. When there are many requests, the recovery time for individual databases can increase. A prolonged outage in a region might cause a high number of geo-restore requests for disaster recovery. The number of concurrent restore requests that are processed in the target regionįor a large or very active database, the restore might take several hours.The network bandwidth if the restore is to a different region.The amount of activity that needs to be replayed to recover to the restore point.The number of transaction logs involved.Several factors affect the recovery time to restore a database through automated database backups: If the actual amount of used space is less than the amount of storage included, you can avoid this extra cost by setting the maximum database size to the included amount. The extra cost happens when the maximum size of the restored database is greater than the amount of storage included with the target database's service tier and service objective.įor pricing details of extra storage, see the SQL Database pricing page.

When you're using the Standard or Premium service tier in the DTU purchasing model, your database restore might incur an extra storage cost.

Database restore operations don't restore the tags of the original database.

You can't overwrite an existing database during restore.

If you configured long-term retention (LTR), you can also create a new database from any long-term retention backup on any server.

Create a new database on any server in any other region, recovered to the point of the most recent replicated backups.

Create a new database on any server in the same region, recovered to the time of a recent backup.

Create a database on the same server, recovered to the deletion time for a deleted database.

Create a new database on the same server, recovered to a specified point in time within the retention period.

The following options are available for database recovery through automated backups: This built-in capability is available for all service tiers and compute sizes. For Azure SQL Managed Instance, see Restore a database from a backup in Azure SQL Managed Instance.Īutomated database backups help protect your databases from user and application errors, accidental database deletion, and prolonged outages. This article provides steps to recover any database from a backup in Azure SQL Database, including Hyperscale databases.

Restore data from .dbs file dbschema