Chapter 13. SQL Azure and relational data
This chapter covers
- Leveraging the power of SQL Server for cloud applications
- Easy ways of migrating an on-premises database to the cloud
- Avoiding potholes during migrations
Most applications that work with data today use a relational data model. It’s a model we’re all familiar with, and we know how to manage and develop with it. SQL Server has been with us for many years, and it’s going to be with us as we move into the cloud.
Over the years, SQL Server has matured to meet the different needs of its customers. It started as a spunky departmental server and moved into the desktop space, mobile device space, and the enterprise space. The relational data engine has been the first component to make each of these moves. The rest of the components usually follow shortly after, such as Integration Services (SSIS), Reporting Services (SSRS), and Analysis Services (SSAS). The cloud isn’t any different. The SQL Server team is bringing the data engine to the cloud first, and the rest of the components of the system will follow it quickly.
When Azure was first released as a CTP in November of 2008 at the PDC, SQL Azure wasn’t on stage. There was something like SQL involved, but it wasn’t a relational engine. It was more like the Azure Table service, but geared for true enterprise needs (beyond the massive scale Tables gives you).