Book Image

Professional Azure SQL Managed Database Administration - Third Edition

By : Ahmad Osama, Shashikant Shakya
Book Image

Professional Azure SQL Managed Database Administration - Third Edition

By: Ahmad Osama, Shashikant Shakya

Overview of this book

Despite being the cloud version of SQL Server, Azure SQL Database and Azure SQL Managed Instance stands out in various aspects when it comes to management, maintenance, and administration. Updated with the latest Azure features, Professional Azure SQL Managed Database Administration continues to be a comprehensive guide for becoming proficient in data management. The book begins by introducing you to the Azure SQL managed databases (Azure SQL Database and Azure SQL Managed Instance), explaining their architecture, and how they differ from an on-premises SQL server. You will then learn how to perform common tasks, such as migrating, backing up, and restoring a SQL Server database to an Azure database. As you progress, you will study how you can save costs and manage and scale multiple SQL databases using elastic pools. You will also implement a disaster recovery solution using standard and active geo-replication. Finally, you will explore the monitoring and tuning of databases, the key features of databases, and the phenomenon of app modernization. By the end of this book, you will have mastered the key aspects of an Azure SQL database and Azure SQL managed instance, including migration, backup restorations, performance optimization, high availability, and disaster recovery.
Table of Contents (14 chapters)
13
Index

Geo-restoring databases

A geo-restore allows you to restore a database from a geo-redundant backup to any available Azure SQL servers and SQL Managed Instance, irrespective of the region.

The automatic backups of Azure SQL Database and SQL Managed Instance are geo-redundant by default, and are copied to a paired Azure region as and when they are taken. There is a maximum delay of one hour when copying a database to a paired geographical location. Therefore, in the case of a disaster, there can be up to an hour of data loss:

Geo-replication to a different geographical location

Figure 5.26: Geo-replication to a different geographical location

Geo-restore can be used to recover a database if an entire region is unavailable because of a disaster:

Using geo-restore in the case of the unavailability of an entire region

Figure 5.27: Use of geo-restore in the case of unavailability of an entire region

The most recent full and differential backups are used to perform a geo-restore.

Geo-restore doesn't support PITR. It is the most basic disaster...