Good summary of techniques to backup and restore SQL Azure databases, as well as some thoughts on features that future tools will provide.
Similar Posts
Using MSBuild to deploy to multiple Windows Azure environments
Excellent Blog post from Tom Hollander on how to deploy applications to Azure using MSBuild. Click here to open link…
Gaining Performance Insight into SQL Azure
Since the SQL Profiler is not currently supported for SQL Azure, this article lists a few alternatives on how to measure query performance… Click here to open link…
Windows Azure Insider November 2013 – Migrating Database Workloads to the Cloud
In the November 2013 issue of the Windows Azure Insider column for MSDN Magazine, Bruno and I talk about the different techniques and technical requirements that you should keep in mind when migrating SQL Server databases from on-premises to the cloud, providing guidance for Virtual Machine specifications and tools. The article can be found here:…
Windows Azure Insider June 2013 – Architecting Multi-Tenant Applications in Windows Azure
One of the biggest challenges that companies face when migrating applications to Windows Azure is going from a single to a multi-tenant approach, which means that some of the compute and data resources are shared by their customers. We take a look at four different areas affected by this process: – Identity and security –…
Mark your calendars! Windows Azure OSS Summit in India, February 2013
Following the successful Windows Azure OSS Summit that I presented in Paris with David Makogon, Bhushan Nene, and Karandeep Anand; we are now flying around the world to meet with Windows Azure developers in India, where we will be visiting three different cities: Mumbai, Pune and Bangalore. We will talk about the latest features incorporated…
Windows Azure Domain Name System Improvements
When you publish an application to Windows Azure, it gets its own subdomain in cloudapp.net. In order to make name resolution even faster (particularly outside the USA), the Domain Name System (DNS) used by Azure is moving to a new globally distributed infrastructure. As the article mentions, there is no customer action required. http://blogs.msdn.com/b/windowsazure/archive/2010/09/24/windows-azure-domain-name-system-improvements.aspx