Are you a SQL Server DBA who is now being asked to migrate databases to Windows Azure SQL Database
(WASD)? Are you a developer who is writing code for a cloud service that shall use SQL Database as the back-end?
This is a series of blogs by Microsoft CSS engineers for guidance & strategies you can use to make a smooth transition to this new platform. The content is based on issues encountered while supporting customers that were once in your shoes and the lessons learned in the process.
There already is a vast amount of documentation for the various aspects of WASD in MSDN. This blog series aims to provide a summarized version with which you can get started and fills gaps where applicable so that you can get things done faster.
In this first installment of the blog series let us start the series by understanding some common terminology when it comes to WASD.
Note that traffic between data centers flows over the internet – which is why most customers host their application and database in the same data center for best performance.
From an end-user perspective, you need to understand the following terms
Additional In-depth information about the architecture of WASD can be found here.
For SQL Server DBA's, a majority of the concepts that you know about SQL Server on premise still apply to WASD. Some of the key differences that you should be aware of are as follows:
For .Net Developers here are some common terminology that you shall encounter while developing applications for WASD
Author: - Rohit Nayak (@sqlrohit)
Reviewers: - Keith Elmore, José Batista-Neto
Escalation Services, Microsoft