Insight into Microsoft SQL Azure patching process

You could be completely oblivious to SQL Azure patching process and successfully use SQL Azure – “SQL Azure team is responsible for patching SQL Azure – you don’t need to download, install, or worry about availability of data during patching. SQL Server DBA usually has concerns when updating SQL Server, usually around successful installation and […]

You could be completely oblivious to SQL Azure patching process and successfully use SQL Azure – “SQL Azure team is responsible for patching SQL Azure – you don’t need to download, install, or worry about availability of data during patching. SQL Server DBA usually has concerns when updating SQL Server, usually around successful installation and post installation data accessibility. We’re going to try to address these concerns and how they relate to SQL Azure, which’s a completely fail-tolerant system designed to allow for rolling updates without interruption to service. This means that when updates are applied there’s no interruption in your ability to access your data. We apply two types of patches to SQL Azure, “operating system updates and service updates”. Both types of updates can cause an established SQL connection to be dropped. For this reason, and others, you need to make sure that your code is designed to try to reestablish a connection to SQL Azure and handle connection pool correctly on connection loss,” explains Microsoft. For detailed information on Operating System Patches, Service Updates, and Data Loss from Updates;

More info: Patching SQL Azure