In this episode with Dani Ljepava, we will show you how to manually trigger a planned failover on SQL Managed Instance to test your applications for fault tolerance and will talk about best practices for your applications to achieve tolerance to transient faults typical for the cloud environments. Transient faults in the cloud (for example software patching, security updates, failover, and similar) include a momentary loss of network connectivity, temporary unavailability of a service, or timeouts when service is busy. These faults are often self-correcting due to which your applications need to be able to handle such occurrences with the appropriate retry logic. While migrating legacy apps to the cloud or developing new cloud-born apps, it is strongly advised to ensure that your applications follow the best practices disclosed in this episode helping you build cloud-ready apps.

0:00 Introduction
0:46 About Dani Ljepava
1:30 Transient errors in the cloud
2:50 Cloud Ready Apps
4:07 Understanding failover as part of HA on SQL MI
6:00 Demo: User-initiated failover on SQL Managed Instance
11:35 How to check if failovers occurred
12:35 Best practices

✔️ Resources:
User-initiated manual failover on SQL Managed Instance: https://aka.ms/mifailover-techblog

📌 Let's connect:
Twitter: Dani Ljepava,   / danimir  
Twitter: Anna Hoffman,   / analyticanna  
Twitter: AzureSQL, https://aka.ms/azuresqltw

🔴 To check out even more Data Exposed episodes, see our playlist: https://aka.ms/dataexposedyt

🔔 Subscribe to our channels for even more SQL tips:
Microsoft Azure SQL: https://aka.ms/msazuresqlyt
Microsoft SQL Server: https://aka.ms/mssqlserveryt
Microsoft Developer: https://aka.ms/microsoftdeveloperyt

#AzureSQLManagedInstance #AzureSQLMI #AzureSQL